1 |
On 10/15/15 4:14 PM, Zac Medico wrote: |
2 |
> On 10/15/2015 01:06 PM, Anthony G. Basile wrote: |
3 |
>> On 10/15/15 3:15 PM, Zac Medico wrote: |
4 |
>>> In portage, @world = @profile + @selected + @system, which means that |
5 |
>>> @profile is protected from depclean since it's a part of @world. |
6 |
>>> |
7 |
>>> [1] https://bugs.gentoo.org/show_bug.cgi?id=532224 |
8 |
>> I thought so but wasn't sure and was about to test. Both @system and |
9 |
>> @profile are controlled via the packages file in portage and stack. |
10 |
>> Packages in @system lead with an * while @profile don't. @system |
11 |
>> packages have incomplete dependency specifications while @profile have |
12 |
>> full. |
13 |
> Right. |
14 |
> |
15 |
>> This affects more than just emerge's ability to parallelize, no? |
16 |
> Having complete dependency specifications could be useful for some other |
17 |
> things, but allowing for more aggressive parallelization is one of the |
18 |
> most obvious advantage. |
19 |
|
20 |
Okay, good because that fits my understanding of how we'd be dividing |
21 |
@system from @profile. |
22 |
|
23 |
@system = the bare set that we need in an stage3 in order to build |
24 |
another stage3 via the catalyst process. so the way this works is that |
25 |
you unpack a stage3, chroot into it, and then do a `ROOT=/some/new/root |
26 |
emerge @system` to prepare a pristine new root. that root then seeds |
27 |
your stage2 at which point your rebuild your toolchain. then that seeds |
28 |
your new stage3 in which you rebuild @system. |
29 |
|
30 |
So that defines @system from the point of view of using a current stage3 |
31 |
to give birth to a next generation stage3. But that may not be what you |
32 |
want to release, eg. do you need any networking stuff in there? This |
33 |
gave birth to the idea of a stage4 which would have the added goodies |
34 |
needed for an end user to grow a system from our release tarball. |
35 |
vapier is suggesting using @profile for the extra needed beyond @system |
36 |
for the release. So at all points except the very end, you just use |
37 |
@system for building because that's all you need, and then finally you |
38 |
produce an @system+@profile for release. |
39 |
|
40 |
-- |
41 |
Anthony G. Basile, Ph.D. |
42 |
Gentoo Linux Developer [Hardened] |
43 |
E-Mail : blueness@g.o |
44 |
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA |
45 |
GnuPG ID : F52D4BBA |