-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nick Cunningham wrote: > > > 2009/1/13 Chris Lieb <chris.l...@gmail.com <mailto:chris.l...@gmail.com>> > > I've noticed lately on the ML that people have been talking about using > package sets, such as @world and @installed. I figured it was a part of > portage 2.1.6* since using @world with 2.1.4* would result in an error > message about an invalid package atom. However, after upgrading to > portage 2.1.6.4, I still get the same error when doing something like > 'emerge -up @world'. > > What are these package sets? What is the difference between 'emerge -up > world' and 'emerge -up @world'? Why don't these package sets ever work > for me? > > Thanks, > Chris > > > A set is basically just group of packages, you can either define you own > using /etc/portage/ or using gentoo provided ones like @world and > @system (which will replace the current emerge system/world usage > eventually), aswell as useful sets such as @live-rebuild (any package > that uses a cvs/svn/git eclass, so basically any -9999 ebuild) and > @module-rebuild which is handy for rebuilding kernel modules. Also id > imagine meta-packages will eventually move over to sets as it makes > rebuilding everything or removing it much easier, currently theres only > kde4 that makes large usage of sets but id imagine once portage 2.20 > goes stable we'l see great set adoption. > An easy way to see what sets are available is to use the emerge > --list-sets command. > > -Nick
Thanks for the info. The @module-rebuild should come in handy. Any idea on when we'll see 2.2* hit stable? Thanks again, Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEcBAEBAgAGBQJJbO1pAAoJEJWxx7fgsD+CClQH/iJudCvbWQmx5IT/CbGL7Rl2 N5TbYtTWhwGgd4xrhPJvlT3MvU4I207+W40lqmtnftaLQaPu+L4nzDervqsh3dlW GPnq1u8v0ASksip/4ZIeC1jMPMTmjcCFagXPiZoouxvZd9YI83xxkLReZbmcniap 8BFGgFVn4M3iGWpma4h+ceYOECGjOxdQTDI5kcH31PHVBVzinYgWj6gm9SbRLEhf 7H0rS00eDSPndeE6192MBR4BY+gx+FbkmlwxTc7UzGVnCyAZCGN3YC+Sr2s0JwGX VGtNV+mAcuk3byS6V2d0hxvzcMuHn3o6VrgspvDF6wda5wnwjjAjkW023baS3RU= =QWDy -----END PGP SIGNATURE-----
