With the current portage, if a user wants to perform a package's ./configure step by hand, the process is rather convoluted. # ebuild foo-x.y.z.ebuild fetch digest unpack # cd /var/tmp/portage/foo-x.y.z/work/foo-x.y.z # ./configure # make # touch ../../.compiled # ebuild /usr/portage/bar/foo/foo-x.y.z.ebuild merge It probably shouldn't be this hard.
yes, we could write a front-end app for ./configure that allows tweaks to be injected easily. But I'd rather integrate this into some kind of new USE system that will track (record) user-specified tweaks so that they don't have to specify them every time they build the package again.
*** Bug 5898 has been marked as a duplicate of this bug. ***
A file in "/etc/" with a mapping from ebuilds to configure options would be enough for me, with perhaps a "USE" variable (Or portage feature?) to turn it on. Editing the ebuild manually isn't a huge deal, (easier than the manual ./configure process) but remembering the changes between "emerge update"(s) is a pain.
how about adding a -- option to emerge such that all further options will be passed to ./configure? I think this is what startx does- all options after startx are passed to startx, but all options after -- are passed to X i.e. startx xterm -- :1 layout=singlehead an example of using this with emerge would be emerge --nodeps xpilot -- --prefix=/usr/games/
Considering how often you'd do this, it's hardly that convoluted. Since this bug is so freaking old, can we mark this as either 'later' or 'invalid'?
EXTRA_ECONF is in portage since ~2.0.42 just not made public because it's not sticky yet.
Created attachment 505056 [details, diff] How
