Move environment.bz2 extraction from ebuild.sh to doebuild() on
authorZac Medico <zmedico@gentoo.org>
Thu, 29 Nov 2007 20:24:05 +0000 (20:24 -0000)
committerZac Medico <zmedico@gentoo.org>
Thu, 29 Nov 2007 20:24:05 +0000 (20:24 -0000)
commit4f4287014f5742bd08b8c950d7cfdf2fd52ea921
treee85dead2e3f2fb16fa6a271163edb448c517d6f8
parent7533586dcc2c0351da28da56b9e6a2a1b9ea004d
Move environment.bz2 extraction from ebuild.sh to doebuild() on
the python side. The python will be able to use it's awareness
of the ${T}/environment to decide what type of ebuild environment
should be generated. For example, if the ebuild environment
should be able to unset variables that have been inherited from
the calling environment, the existence of ${T}/environment
will indicate that the ebuild environment should be isolated from
the calling environment.

svn path=/main/trunk/; revision=8753
bin/ebuild.sh
bin/isolated-functions.sh
pym/portage/__init__.py