On Fri, 2008-02-08 at 10:14 +0100, Fabian Groffen wrote: > On 04-02-2008 20:56:21 +0000, Alan Hourihane wrote: > > > Then run portage, and check if the var is set. Also, during > > > compilation, it should be stored in the environment file in the "temp" > > > dir of your var/tmp/portage/cat/pkg/. > > > > O.k. it is there on the echo, but something is removing it in the > > ebuild.sh script as it's failed again. I'm pretty sure it's the > > filter_readonly_variables() doing it, then it puts it back when it > > sources the environment later. > > > > But that's too late, because if UNIXMODE is removed I lose, and sed > > breaks. > > It appears that the sed that fails for you is a sed that is run in the > middle of the process to filter the environment, just after the env is > cleaned, and just before the env is restored. > > In your case it is necessary to inject UNIXMODE in ebuild.sh as you did, > the ebuild should in any case always see UNIXMODE as you set it in your > environment. > > The only thing I can do, is to make a special file that is sourced by > Portage in ebuild.sh that contains UNIXMODE for you. It is quite ugly, > but the only thing that will help you to keep a working Portage over > upgrades.
Right. Thanks Fabian. Alan. -- [email protected] mailing list
