| 1 |
Zac Medico posted on Tue, 06 Dec 2011 15:45:26 -0800 as excerpted: |
| 2 |
|
| 3 |
> We can easily roll packages.default into the set support that's in |
| 4 |
> stable portage (no need for full-blown sets.conf support). Currently, in |
| 5 |
> stable portage, we have: |
| 6 |
> |
| 7 |
> @world = @selected + @system |
| 8 |
> |
| 9 |
> How about if we add an optional @default set that's generated from |
| 10 |
> pacakges.default in the user's profile? The @default set would be pulled |
| 11 |
> in by @selected when @default is listed in /var/lib/portage/world_sets |
| 12 |
> (in stable portage, @selected currently only pulls in atoms from |
| 13 |
> /var/lib/portage/world). |
| 14 |
|
| 15 |
If @selected only pulls in /var/lib/portage/world , what pulls in |
| 16 |
/var/lib/portage/world_sets ? You mention it, but don't say what pulls |
| 17 |
it in, if as you say @selected doesn't. |
| 18 |
|
| 19 |
-- |
| 20 |
Duncan - List replies preferred. No HTML msgs. |
| 21 |
"Every nonfree program has a lord, a master -- |
| 22 |
and if you use the program, he is your master." Richard Stallman |
Archives