Bother, hit return instead of tab there. Sorry about the empty post. Anyway,
Two quick updates to the ebuild(5) man page for you to fix.
The location of the build directory is set by the
BUILD_PREFIX variable in /etc/make.defaults (it
defaults to /tmp/portage.)
That should read /usr/tmp/portage for the default, not /tmp/portage. Then again,
it looks like BUILD_PREFIX is going out of style?
Note: Currently, Portage doesn't clean up after a package
has been created or merged.
'emerge <package>' will clean up the build directory automagically, and
since emerge is the command most people think of when hearing "Portage"
then this statement isn't true anymore.
Minor update. It should read /var/tmp/portage, not /usr/tmp/portage. The one
points to the other on a stock Gentoo box, but since it might not it's best to
get it right.
Also, quick grep'ing through the code shows that BUILD_PREFIX isn't really
changeable at all, you'll have to use PORTAGE_TMPDIR if you want to change where
things are built. I.e. this is done in portage.py:doebuild() :
In other words, a rewrite of that part of the man page is in order. Thanks.
thanks for the updates, I guess It all comes back to me to keep this cleaned up
(that's waht you get for making some updates LOL). J/K
Thanks for the updates, I'll get them in very soon and should be reflected in
next portage release.
While you're updating... The manpage doesn't document the econf directive
(although it is referred to in the example).
added econf to ebuild.5