| 1 |
On Tue, 05 Jan 2010 18:41:35 +0100, Alex Schuster <wonko@×××××××××.org> |
| 2 |
wrote: |
| 3 |
|
| 4 |
> Zeerak Waseem writes: |
| 5 |
> |
| 6 |
>> I have some questions about sets: |
| 7 |
>> 1) Sets are just files with one package per line in /usr/portage/sets, |
| 8 |
>> right? |
| 9 |
> |
| 10 |
> I think it's /etc/portage/sets instead. And there are also meta-sets like |
| 11 |
> system, world, module-rebuild, preserved-rebuild and more, defined in |
| 12 |
> /usr/share/portage/config/sets.conf. There is a little documentation in |
| 13 |
> the emerge man page, but I have no idea where else sets are documented. |
| 14 |
> |
| 15 |
>> 2) Can a set be included in the world file? |
| 16 |
> |
| 17 |
> I don't think so, sets go into /var/lib/portage/world_sets. |
| 18 |
> |
| 19 |
>> 3) With set files in /usr/portage/sets and running "emerge -u @foo" |
| 20 |
>> portage yields that @foo isn't a valid package atom, any idea why this |
| 21 |
>> is? |
| 22 |
> |
| 23 |
> Your portage is too old? In case of an error, you should get an "emerge: |
| 24 |
> There are no sets to satisfy 'foo'" message, and a list of known sets. |
| 25 |
> |
| 26 |
> Wonko |
| 27 |
> |
| 28 |
|
| 29 |
Ah well, having the sets in the wrong place would give me an error. |
| 30 |
And regarding portage version, weren't sets included in v. 2.x.x? My |
| 31 |
portage version is 2.1.7.16, anything above seems to be hardmasked... |
| 32 |
|
| 33 |
-- |
| 34 |
Zeerak |
Archives