From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Emerge question: What's with the @?
Date: Tue, 13 Jan 2009 13:54:52 -0600 [thread overview]
Message-ID: <58965d8a0901131154x1bc7630r69cf841208b4fa72@mail.gmail.com> (raw)
In-Reply-To: <gkiqh9$k2i$1@ger.gmane.org>
On Tue, Jan 13, 2009 at 1:37 PM, Chris Lieb <chris.lieb@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Nick Cunningham wrote:
>>
>>
>> 2009/1/13 Chris Lieb <chris.lieb@gmail.com <mailto:chris.lieb@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
"When it's ready" I guess is the standard answer there. :) it's masked
in ~arch as well, but you can simply unmask it if you want to use it.
That's what I did. I have these sets available in my system currently:
downgrade
installed
live-rebuild
module-rebuild
preserved-rebuild
security
system
unavailable
world
@live-rebuild is especially handy to rebuild live cvs/svn/etc ebuilds
(that -9999 stuff)
Paul
next prev parent reply other threads:[~2009-01-13 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 19:09 [gentoo-user] Emerge question: What's with the @? Chris Lieb
2009-01-13 19:12 ` Nikolay Mikheev
2009-01-13 19:22 ` Nick Cunningham
2009-01-13 19:37 ` [gentoo-user] " Chris Lieb
2009-01-13 19:52 ` Nick Cunningham
2009-01-13 19:54 ` Paul Hartman [this message]
2009-01-13 20:17 ` Nick Cunningham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58965d8a0901131154x1bc7630r69cf841208b4fa72@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox