| 1 |
2009/1/13 Chris Lieb <chris.lieb@×××××.com> |
| 2 |
|
| 3 |
> I've noticed lately on the ML that people have been talking about using |
| 4 |
> package sets, such as @world and @installed. I figured it was a part of |
| 5 |
> portage 2.1.6* since using @world with 2.1.4* would result in an error |
| 6 |
> message about an invalid package atom. However, after upgrading to |
| 7 |
> portage 2.1.6.4, I still get the same error when doing something like |
| 8 |
> 'emerge -up @world'. |
| 9 |
> |
| 10 |
> What are these package sets? What is the difference between 'emerge -up |
| 11 |
> world' and 'emerge -up @world'? Why don't these package sets ever work |
| 12 |
> for me? |
| 13 |
> |
| 14 |
> Thanks, |
| 15 |
> Chris |
| 16 |
> |
| 17 |
> |
| 18 |
A set is basically just group of packages, you can either define you own |
| 19 |
using /etc/portage/ or using gentoo provided ones like @world and @system |
| 20 |
(which will replace the current emerge system/world usage eventually), |
| 21 |
aswell as useful sets such as @live-rebuild (any package that uses a |
| 22 |
cvs/svn/git eclass, so basically any -9999 ebuild) and @module-rebuild which |
| 23 |
is handy for rebuilding kernel modules. Also id imagine meta-packages will |
| 24 |
eventually move over to sets as it makes rebuilding everything or removing |
| 25 |
it much easier, currently theres only kde4 that makes large usage of sets |
| 26 |
but id imagine once portage 2.20 goes stable we'l see great set adoption. |
| 27 |
An easy way to see what sets are available is to use the emerge --list-sets |
| 28 |
command. |
| 29 |
|
| 30 |
-Nick |
Archives