I want to build net-misc/openssh with configure option --with-default-path. But openssh-*.ebuild uses ./configure instead of econf, so I cannot use EXTRA_ECONF. Would you change to use not ./configure but econf? Reproducible: Always Steps to Reproduce: 1. 2. 3.
unless daniel feels like doing it, econf doesnt give any advantage with its default arguements since the openssh uses different values anyways edit the ebuild for now
I want to set --with-default-path. ./configure in net-misc/openssh/openssh-*.ebuild does not use this option. so I think I can specify my own value with EXTRA_ECONF. env EXTRA_ECONF='--with-default-path=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin' emerge -v net-misc/openssh
so edit the ebuild and add that option or do `env PATH="/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin" emerge openssh`
Thanks for comment. As a result of reading configure script (including OpenSSH-3.8p1) and actually trying `env PATH=... emerge openssh`, PATH has no effect to --with-default-path. Now, I use PORTDIR_OVERLAY and edit openssh-*.ebuild under PORTDIR_OVERLAY directory. (At first, edit ebuild file in portage directory as SpanKY's comment. However, since over write every `emerge sync`, I was used PORTDIR_OVERLAY) cp -R /usr/portage/net-misc/openssh PORTDIR_OVERLAY/net-misc/openssh cd PORTDIR_OVERLAY/net-misc/openssh mv openssh-3.8_p1.ebuild openssh-3.8_p1.ebuild.orig sed -e 's@./configure@econf@' openssh-3.8_p1.ebuild.orig > openssh-3.8_p1.ebuild env ACCEPT_KEYWORDS=~x86 \ EXTRA_ECONF='--with-default-path=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin' \ emerge -v =net-misc/openssh-3.8_p1 Although this method may be used, whenever new portage comes out, copy files to PORTDIR_OVERLAY and edit ebuld is troublesome, so I want maintainer to change into econf from ./configure so that EXTRA_ECONF can be used. Would you surely teach the reason for future reference, if reasonable using not econf but configure?