| 1 |
On Tue, 5 Jan 2010 18:41:35 +0100 |
| 2 |
Alex Schuster <wonko@×××××××××.org> 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 |
|
| 11 |
There are other kind of sets, for example, dynamic ones, from the |
| 12 |
output of a given command, which allow you to do things like preserving |
| 13 |
N last slots of package (gcc, kernel, etc) or creating your own |
| 14 |
dependency trees. Important file here is /etc/portage/sets.conf. |
| 15 |
|
| 16 |
|
| 17 |
> I think it's /etc/portage/sets instead. And there are also meta-sets like |
| 18 |
> system, world, module-rebuild, preserved-rebuild and more, defined in |
| 19 |
> /usr/share/portage/config/sets.conf. There is a little documentation in |
| 20 |
> the emerge man page, but I have no idea where else sets are documented. |
| 21 |
|
| 22 |
It's all documented in html pages, which will be installed if you'll |
| 23 |
emerge portage with USE=doc, just look at the |
| 24 |
/usr/share/doc/portage-2.2*/html/index.html |
| 25 |
|
| 26 |
|
| 27 |
> > 2) Can a set be included in the world file? |
| 28 |
> |
| 29 |
> I don't think so, sets go into /var/lib/portage/world_sets. |
| 30 |
> |
| 31 |
> > 3) With set files in /usr/portage/sets and running "emerge -u @foo" |
| 32 |
> > portage yields that @foo isn't a valid package atom, any idea why this |
| 33 |
> > is? |
| 34 |
> |
| 35 |
> Your portage is too old? In case of an error, you should get an "emerge: |
| 36 |
> There are no sets to satisfy 'foo'" message, and a list of known sets. |
| 37 |
> |
| 38 |
> Wonko |
| 39 |
> |
| 40 |
|
| 41 |
-- |
| 42 |
Mike Kazantsev // fraggod.net |
Archives