On Tue, 5 Jan 2010 18:41:35 +0100 Alex Schuster <wo...@wonkology.org> wrote:
> Zeerak Waseem writes: > > > I have some questions about sets: > > 1) Sets are just files with one package per line in /usr/portage/sets, > > right? > There are other kind of sets, for example, dynamic ones, from the output of a given command, which allow you to do things like preserving N last slots of package (gcc, kernel, etc) or creating your own dependency trees. Important file here is /etc/portage/sets.conf. > I think it's /etc/portage/sets instead. And there are also meta-sets like > system, world, module-rebuild, preserved-rebuild and more, defined in > /usr/share/portage/config/sets.conf. There is a little documentation in > the emerge man page, but I have no idea where else sets are documented. It's all documented in html pages, which will be installed if you'll emerge portage with USE=doc, just look at the /usr/share/doc/portage-2.2*/html/index.html > > 2) Can a set be included in the world file? > > I don't think so, sets go into /var/lib/portage/world_sets. > > > 3) With set files in /usr/portage/sets and running "emerge -u @foo" > > portage yields that @foo isn't a valid package atom, any idea why this > > is? > > Your portage is too old? In case of an error, you should get an "emerge: > There are no sets to satisfy 'foo'" message, and a list of known sets. > > Wonko > -- Mike Kazantsev // fraggod.net
signature.asc
Description: PGP signature
