From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage getting mixed up with USE?
Date: Fri, 24 Jun 2011 00:31:38 +0200 [thread overview]
Message-ID: <3223478.mY2kb5XGVq@nazgul> (raw)
In-Reply-To: <20110623230600.0a4b2b7c@digimed.co.uk>
On Thursday 23 June 2011 23:06:00 Neil Bothwick did opine thusly:
> > > b) it breaks the way portage displays his informations.
> > > Without
> > > autounmask the display of emerge shows what he is going to
> > > do. With autounmask it shows what needs to be done.
> >
> >
> >
> > That is probably the most evil of all your reasons. There's an
> > old dev joke about The Law Of Unintended Consequences, and it
> > applies here - portage is now suddenly doing something new and
> > 180 different from what it used to do. The normal response if
> > "WTF?" followed by lots of indignation
>
> Ah, the old "we do it that way because that's the way it's always
> been done" argument. Yes, it is different, yes, it may be confusing
> when you first encounter the change - but that doesn't make it bad.
The thing itself is neither inherently good nor bad. Implementing it
in this way is bad.
Why?
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?
Imagine if tcpwrappers did this. Imagine that hosts.deny was dropped
and hosts.allow retained, also imagine that the desired config file
name becomes hosts.tcpd but it will use hosts.allow if hosts.tcpd is
not found. Now also imagine that the default interpretation of
hosts.tcpd is now default deny, explicit allow.
All your rules now suddenly invert. Chaos ensues.
Sure, it's a contrived example, but it's also a very good example of
why one never suddenly and without warning changes default behaviour
to the opposite.
Few people will argue against the existence of the new unmask options.
Folk who want it can use it. Just don't make it the default in such a
way that it catches old time users by surprise.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-06-23 22:40 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 [this message]
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
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=3223478.mY2kb5XGVq@nazgul \
--to=alan.mckinnon@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