| 1 |
On 10/28/2009 03:42 PM, Mike Frysinger wrote: |
| 2 |
> not sure why we're still even using this stage[123] system. seems like |
| 3 |
> catalyst could be implemented in all of three commands: |
| 4 |
> ROOT=/tmp/stage3_pre emerge system -e |
| 5 |
> chroot /tmp/stage3 env ROOT=/tmp/stage3 emerge system -e |
| 6 |
> |
| 7 |
> then we wouldnt need these USE="build bootstrap" hacks nor would we need the |
| 8 |
> packages.build cruft |
| 9 |
|
| 10 |
I added a target called 'system' over 6 months ago in the catalyst-3 branch in |
| 11 |
git (now the master branch) that does exactly this. There are a few things |
| 12 |
missing compared to a "real" stage3, but it's just stuff like .ph files and |
| 13 |
other random things that can't be generated when $ROOT != "/". |
| 14 |
|
| 15 |
I had considered backporting it to catalyst-2, but I'd rather not touch the |
| 16 |
catalyst-2 code any more than necessary at this point. |
| 17 |
|
| 18 |
If anyone wants to play with it, you can get catalyst-3 by using the |
| 19 |
dev-util/catalyst-9999 ebuild in the tree. However, I cannot guarantee that it's |
| 20 |
in a working state at any given time. |
| 21 |
|
| 22 |
-- |
| 23 |
Andrew Gaffney http://dev.gentoo.org/~agaffney/ |
| 24 |
Gentoo Linux Developer Catalyst/Genkernel + Release Engineering Lead |
Archives