From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Major update problem
Date: Thu, 10 Feb 2011 05:52:43 +0000 (UTC) [thread overview]
Message-ID: <pan.2011.02.10.05.52.43@cox.net> (raw)
In-Reply-To: 877hd9vj3d.fsf@phoenix.asynchronous.org
Josh Sled posted on Wed, 09 Feb 2011 01:05:10 -0500 as excerpted:
> Duncan <1i5t5.duncan@cox.net> writes:
>> Jonathan Callen posted on Tue, 08 Feb 2011 16:29:35 -0500 as excerpted:
>>
>>> Portage 2.1 only has support for 3 sets: @world, @system, and
>>> @selected. All of the other support for sets has been disabled
>>> internally in the code but is otherwise present to allow easier
>>> merging between the 2.1 and master branches in git.
>>
>> Thanks. I was wondering how I'd missed that big news!
>
> Well, it's still only in unstable. :) I'd hope before this goes into
> stable, a News item (at least!) is created to guide users into how their
> behavior needs to change.
So then sets (beyond the three above) are unmasked to ~arch, at least,
then? Because last I knew they were in the (last I knew) hard-masked 2.2
series, only. So even unmasking them to ~arch would be big news, here.
(And, since I run ~arch, if they're ~arch keyworded and not in
package.mask, they're not masked, from my viewpoint. They might be ~arch,
but that's not masked, but ~arch. Masked means either an entry in
package.mask or KEYWORDS="", to me.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2011-02-10 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 12:27 [gentoo-amd64] Major update problem Paul Stear
2011-02-07 13:27 ` Paul Stear
2011-02-08 2:45 ` [gentoo-amd64] " Duncan
2011-02-08 21:29 ` Jonathan Callen
2011-02-09 3:03 ` Duncan
2011-02-09 6:05 ` Josh Sled
2011-02-10 5:52 ` Duncan [this message]
2011-02-07 13:41 ` [gentoo-amd64] " Arttu V.
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=pan.2011.02.10.05.52.43@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@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