From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge sets syntax (@world vs. world)
Date: Wed, 12 Dec 2012 09:03:31 -0600 [thread overview]
Message-ID: <20121212150331.GX8486@server> (raw)
In-Reply-To: <1355313181.4605.140661165059833.3797A1E2@webmail.messagingengine.com>
On Wed, Dec 12, 2012 at 12:53:01PM +0100, Francesco Turco wrote:
> Hello.
>
> A couple of weeks ago I filed a bug because in the Installation Handbook
> I found some references of the "world" set in emerge commands, as
> opposed to "@world": https://bugs.gentoo.org/show_bug.cgi?id=445184
>
> The bug was closed as invalid, and I was told that:
>
> > sets with the @ prefix are a portage-2.2 feature, which is still hardmasked and thus not documented.
>
> The fact is that I have portage-2.1.11.37, not 2.2, and man emerge says:
>
> > When used as arguments to emerge sets have to be prefixed with @ to be recognized.
>
> One possibility is that documentation stick with the stable portage
> package, not the testing one (I have a ~amd64 system only). But I
> checked portage 2.1.11.31 (the latest stable amd64 portage package
> version) and the previous phrase is there, too.
>
> I know it's not a very important issue, but I'd still like to know if
> I'm wrong or not, and why.
Is there even a valid world set in portage before 2.2?
mingdao@server ~ $ eshowkw portage
Keywords for sys-apps/portage:
| | u |
| a a p s | n |
| l m h i m m p s p | u s | r
| p d a p a 6 i p c 3 a x | s l | e
| h 6 r p 6 8 p p 6 9 s r 8 | e o | p
| a 4 m a 4 k s c 4 0 h c 6 | d t | o
---------------+---------------------------+-----+-------
[M]2.1.6.7_p1 | + + + + + + ~ + + + + + + | # 0 | gentoo
2.1.11.9 | + + + + + + ~ + + + + + + | # | gentoo
[I]2.1.11.31 | + + + + + + ~ + + + + + + | o | gentoo
2.1.11.33 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | # | gentoo
2.1.11.36 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | # | gentoo
2.1.11.37 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | o | gentoo
2.2.0_alpha142 | o o o o o o o o o o o o o | # | gentoo
2.2.0_alpha144 | o o o o o o o o o o o o o | # | gentoo
2.2.0_alpha147 | o o o o o o o o o o o o o | # | gentoo
2.2.0_alpha148 | o o o o o o o o o o o o o | o | gentoo
9999 | o o o o o o o o o o o o o | o | gentoo
mingdao@server ~ $ ls -al /var/lib/portage/
total 12
drwxr-sr-x 2 root portage 78 Dec 12 08:10 .
drwxr-xr-x 11 root root 152 Oct 20 22:25 ..
-rw-rw---- 1 root portage 8076 Nov 21 07:26 config
-rw-rw---- 1 root portage 0 Nov 6 08:03 preserved_libs_registry
-rw-r--r-- 1 root portage 1122 Dec 6 14:51 world
-rw-r--r-- 1 root portage 0 Dec 6 14:51 world_sets
Might be why @preserved-rebuild never does anything for me, also.
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
prev parent reply other threads:[~2012-12-12 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 11:53 [gentoo-user] emerge sets syntax (@world vs. world) Francesco Turco
2012-12-12 13:18 ` Alan McKinnon
2012-12-12 14:53 ` Randy Barlow
2012-12-12 18:22 ` Francesco Turco
2012-12-14 10:29 ` Francesco Turco
2012-12-12 14:10 ` Michael Orlitzky
2012-12-12 15:03 ` Bruce Hill [this message]
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=20121212150331.GX8486@server \
--to=daddy@happypenguincomputers.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