1 |
On 12/06/2011 09:21 PM, Duncan wrote: |
2 |
> Zac Medico posted on Tue, 06 Dec 2011 15:45:26 -0800 as excerpted: |
3 |
> |
4 |
>> We can easily roll packages.default into the set support that's in |
5 |
>> stable portage (no need for full-blown sets.conf support). Currently, in |
6 |
>> stable portage, we have: |
7 |
>> |
8 |
>> @world = @selected + @system |
9 |
>> |
10 |
>> How about if we add an optional @default set that's generated from |
11 |
>> pacakges.default in the user's profile? The @default set would be pulled |
12 |
>> in by @selected when @default is listed in /var/lib/portage/world_sets |
13 |
>> (in stable portage, @selected currently only pulls in atoms from |
14 |
>> /var/lib/portage/world). |
15 |
> |
16 |
> If @selected only pulls in /var/lib/portage/world , what pulls in |
17 |
> /var/lib/portage/world_sets ? You mention it, but don't say what pulls |
18 |
> it in, if as you say @selected doesn't. |
19 |
|
20 |
Currently, in portage-2.2.x, @selected pulls in both |
21 |
/var/lib/portage/world and /var/lib/portage/world_sets. If we want, we |
22 |
can easily do it that way in stable too. |
23 |
-- |
24 |
Thanks, |
25 |
Zac |