From: "Sebastian Beßler" <sebastian@darkmetatron.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage getting mixed up with USE?
Date: Fri, 24 Jun 2011 10:00:18 +0200 [thread overview]
Message-ID: <4E044412.7050300@darkmetatron.de> (raw)
In-Reply-To: <20110624011033.09bce3d4@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
Am 24.06.2011 02:10, schrieb Neil Bothwick:
> On Fri, 24 Jun 2011 00:31:38 +0200, Alan McKinnon wrote:
>
>> Because the behaviour changed to something that is the exact opposite
>> without any warning. Portage always used to tell what it will do. Now,
>> simply by leaving the relevant options at the default, it tells me
>> what it should do. How much more contrary to reasonable expectation
>> can you get?
>
> It's not the exact opposite. Portage is still telling you what it needs,
> but all in one go, not one problem at a time.
The feature is not bad, but how it is implemented is.
With autounmask you get a notice that you have something to change, then
look up to the portage presented list and see that the changes are
already there. Then you are wondering why portage says that you have to
do something that is already done and assume it is a bug.
Such a reaction started this thread.
Now that I know how to read it and what to expect I can work with it and
see that it is not so bad after all.
The change was unexpected and contrary to reasonable expectation mainly
because there was no information before or after this change. It needed
this thread to clear how it works and how to read ist.
Greetings
Sebastian
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2011-06-24 8:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 8:18 [gentoo-user] portage getting mixed up with USE? Alan McKinnon
2011-06-22 8:49 ` Daniel Pielmeier
2011-06-22 9:15 ` Alan McKinnon
2011-06-22 9:31 ` Daniel Pielmeier
2011-06-22 9:50 ` Alan McKinnon
2011-06-22 9:47 ` Neil Bothwick
2011-06-22 9:53 ` Alan McKinnon
2011-06-22 10:43 ` Neil Bothwick
2011-06-22 11:54 ` Alan McKinnon
2011-06-22 12:22 ` Daniel Pielmeier
2011-06-22 12:41 ` Alan McKinnon
2011-06-22 14:19 ` Mick
2011-06-22 14:44 ` Neil Bothwick
2011-06-22 15:31 ` Alan McKinnon
2011-06-22 16:05 ` Mick
2011-06-22 16:22 ` Neil Bothwick
2011-06-22 16:30 ` Sebastian Beßler
2011-06-22 16:59 ` Alan McKinnon
2011-06-23 11:31 ` Daniel Pielmeier
2011-06-23 19:40 ` Alan McKinnon
2011-06-22 17:11 ` Sebastian Beßler
2011-06-22 18:22 ` Dale
2011-06-22 19:16 ` Sebastian Beßler
2011-06-22 20:12 ` Alan McKinnon
2011-06-22 22:35 ` Mick
2011-06-22 22:58 ` Neil Bothwick
2011-06-23 1:35 ` Matthew Finkel
2011-06-23 6:59 ` Sebastian Beßler
2011-06-23 19:38 ` Alan McKinnon
2011-06-23 22:06 ` Neil Bothwick
2011-06-23 22:31 ` Alan McKinnon
2011-06-23 22:56 ` Mike Edenfield
2011-06-24 0:05 ` Neil Bothwick
2011-06-24 0:10 ` Neil Bothwick
2011-06-24 8:00 ` Sebastian Beßler [this message]
2011-06-23 20:05 ` Yohan Pereira
2011-06-24 8:11 ` Sebastian Beßler
2011-06-22 10:48 ` Daniel Pielmeier
2011-06-22 11:57 ` Alan McKinnon
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=4E044412.7050300@darkmetatron.de \
--to=sebastian@darkmetatron.de \
--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