| 1 |
On 08/16/2012 08:26 PM, Michael Mol wrote: |
| 2 |
> Ideally, you'd want as narrow a bootstrapping channel as possible. |
| 3 |
> Assuming things start off statically linked, what's the sequence for |
| 4 |
> going from an empty chroot to stage 1, 2, 3...? What are the starting |
| 5 |
> conditions? |
| 6 |
|
| 7 |
We use sys-apps/catalyst, which builds stage1 in a new $ROOT by simply |
| 8 |
extracting a seed stage3 and calling $PORTDIR/scripts/booststrap.sh. The |
| 9 |
stage1 is pretty minimal, but it's enough to generate a new stage3 by |
| 10 |
simply calling emerge -e @system (you can skip stage2 step entirely). |
| 11 |
The stage2 step is just used to rebuild some essential packages for a |
| 12 |
more specialized CHOST, so it's only needed when your stage1 has a |
| 13 |
generic CHOST and you want to build a stage3 with a more specialized CHOST. |
| 14 |
-- |
| 15 |
Thanks, |
| 16 |
Zac |
Archives