1 |
On 10/29/2009 08:56 AM, Mike Frysinger wrote: |
2 |
> On Thursday 29 October 2009 08:34:48 Andrew Gaffney wrote: |
3 |
>> On 10/28/2009 03:42 PM, Mike Frysinger wrote: |
4 |
>>> not sure why we're still even using this stage[123] system. seems like |
5 |
>>> catalyst could be implemented in all of three commands: |
6 |
>>> ROOT=/tmp/stage3_pre emerge system -e |
7 |
>>> chroot /tmp/stage3 env ROOT=/tmp/stage3 emerge system -e |
8 |
>>> |
9 |
>>> then we wouldnt need these USE="build bootstrap" hacks nor would we need |
10 |
>>> the packages.build cruft |
11 |
>> |
12 |
>> I added a target called 'system' over 6 months ago in the catalyst-3 branch |
13 |
>> in git (now the master branch) that does exactly this. There are a few |
14 |
>> things missing compared to a "real" stage3, but it's just stuff like .ph |
15 |
>> files and other random things that can't be generated when $ROOT != "/". |
16 |
> |
17 |
> i'm not entirely sure the second ROOT= is necessary if a clean up script does |
18 |
> a sufficient job of catching all accumulated cruft. i was just throwing the |
19 |
> idea out there again, but seems it isnt terribly necessary if it's been picked |
20 |
> up at some point. |
21 |
> -mike |
22 |
|
23 |
I didn't pay too much attention to what you actually said (aside from ROOT and |
24 |
'emerge -e system'). The catalyst-3 'system' target just does the first command. |
25 |
It's basically the stage1 procedure with @system instead of packages.build. |
26 |
|
27 |
-- |
28 |
Andrew Gaffney http://dev.gentoo.org/~agaffney/ |
29 |
Gentoo Linux Developer Catalyst/Genkernel + Release Engineering Lead |