On 10/29/2009 08:56 AM, Mike Frysinger wrote:
> On Thursday 29 October 2009 08:34:48 Andrew Gaffney wrote:
>> On 10/28/2009 03:42 PM, Mike Frysinger wrote:
>>> not sure why we're still even using this stage[123] system.  seems like
>>> catalyst could be implemented in all of three commands:
>>> ROOT=/tmp/stage3_pre emerge system -e
>>> chroot /tmp/stage3 env ROOT=/tmp/stage3 emerge system -e
>>>
>>> then we wouldnt need these USE="build bootstrap" hacks nor would we need
>>> the packages.build cruft
>>
>> I added a target called 'system' over 6 months ago in the catalyst-3 branch
>>  in git (now the master branch) that does exactly this. There are a few
>>  things missing compared to a "real" stage3, but it's just stuff like .ph
>>  files and other random things that can't be generated when $ROOT != "/".
> 
> i'm not entirely sure the second ROOT= is necessary if a clean up script does 
> a sufficient job of catching all accumulated cruft.  i was just throwing the 
> idea out there again, but seems it isnt terribly necessary if it's been picked 
> up at some point.
> -mike

I didn't pay too much attention to what you actually said (aside from ROOT and
'emerge -e system'). The catalyst-3 'system' target just does the first command.
It's basically the stage1 procedure with @system instead of packages.build.

-- 
Andrew Gaffney                                 http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer            Catalyst/Genkernel + Release Engineering Lead