From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LMpCN-0005GV-Br for garchives@archives.gentoo.org; Tue, 13 Jan 2009 19:45:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 45EEBE0746; Tue, 13 Jan 2009 19:45:14 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 0381DE0746 for ; Tue, 13 Jan 2009 19:45:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 7DFC364686 for ; Tue, 13 Jan 2009 19:45:13 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 required=5.5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h0pO8sFusF1h for ; Tue, 13 Jan 2009 19:45:06 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id BF4E264567 for ; Tue, 13 Jan 2009 19:45:04 +0000 (UTC) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1LMpCA-0003Km-JF for gentoo-user@gentoo.org; Tue, 13 Jan 2009 19:45:02 +0000 Received: from net19h105.itsd.state.ms.us ([205.144.234.105]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Jan 2009 19:45:02 +0000 Received: from chris.lieb by net19h105.itsd.state.ms.us with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Jan 2009 19:45:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Chris Lieb Subject: [gentoo-user] Re: Emerge question: What's with the @? Date: Tue, 13 Jan 2009 13:37:13 -0600 Message-ID: References: <496CE702.6000700@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: net19h105.itsd.state.ms.us User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) In-Reply-To: X-Enigmail-Version: 0.95.7 OpenPGP: id=266AC070; url=subkeys.pgp.net Sender: news X-Archives-Salt: 4b3aafac-e4fc-4d13-9258-0d9936ee9847 X-Archives-Hash: e5187f49b37561821efa8934c78826be -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nick Cunningham wrote: > > > 2009/1/13 Chris Lieb > > > 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-----