From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] PROPERTIES=set for meta-packages that should behave like package sets
Date: Mon, 29 Sep 2008 02:52:09 +0000 (UTC) [thread overview]
Message-ID: <pan.2008.09.29.02.52.08@cox.net> (raw)
In-Reply-To: 48E00B9B.3060600@gentoo.org
Zac Medico <zmedico@gentoo.org> posted 48E00B9B.3060600@gentoo.org,
excerpted below, on Sun, 28 Sep 2008 15:56:27 -0700:
> For example, `emerge kde-meta` would behave as as normal meta-package
> currently does, and `emerge @kde-meta` would reference the same package
> as a set and could thereby trigger different behavior which is
> appropriate for a set.
Ahh... that's rather clearer now. Somehow I missed that bit before.
However, it seems to me we'd have some of the same types of issues we've
previously discussed over the distinction between world and @world. It's
going to be virtually impossible to get some users to see the difference,
with the consequence being that they use the wrong reference (probably
skipping the @ as unnecessary typing) and end up with (to them)
completely unexpected behaviour. How long have we been drilling into
users' heads that they need to use --pretend (or --ask) --verbose to
check that what they intend is really what's going to happen? Yet I just
dealt with a case the other day where someone ended up with something
entirely (to them) unexpected, because they failed to preview what was
going to happen, first.
Going out of our way to (effectively) make things even /more/ confusing
by deliberately creating set-packages that can be referred to as either,
with different behavior in each case, would seem to be the equivalent of
deliberately setting traps for those poor users. (Yes, they /should/
know the difference and it's a PEBCAK if they don't/won't, but
unfortunately that PEBCAK is/can-safely-be-predicted-to-be rather
common...)
So sure, we can institute it as suggested, damn the torpedos, but I
believe it's safely predictable that come a few months hence, after we've
dealt with our tenth person to end up screwing their system as a result,
we're going to rue the day... Never-the-less, it's not my decision.
--
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:[~2008-09-29 2:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 0:21 [gentoo-dev] [RFC] PROPERTIES=set for meta-packages that should behave like package sets Zac Medico
2008-09-28 15:24 ` Marius Mauch
2008-09-28 17:42 ` Zac Medico
2008-09-28 20:26 ` Ciaran McCreesh
2008-09-28 20:44 ` Zac Medico
2008-09-28 20:32 ` Ciaran McCreesh
2008-09-28 20:53 ` Zac Medico
2008-09-28 21:01 ` Ciaran McCreesh
2008-09-28 22:11 ` Zac Medico
2008-09-28 22:28 ` Ciaran McCreesh
2008-09-28 22:56 ` Zac Medico
2008-09-28 23:02 ` Ciaran McCreesh
2008-09-28 23:37 ` Zac Medico
2008-09-29 15:13 ` Bo Ørsted Andresen
2008-09-29 19:52 ` Zac Medico
2008-09-30 4:47 ` Jorge Manuel B. S. Vicetto
2008-09-30 5:31 ` Zac Medico
2008-10-01 4:35 ` [gentoo-dev] " Ryan Hill
2008-10-01 16:37 ` Zac Medico
2008-10-02 2:51 ` Jorge Manuel B. S. Vicetto
2008-10-04 6:05 ` Ryan Hill
2008-10-04 6:42 ` Ryan Hill
2008-10-04 17:17 ` Zac Medico
2008-10-05 17:55 ` Ryan Hill
2008-10-13 2:11 ` Steve Long
2008-10-02 12:19 ` Robert Bridge
2008-09-29 2:52 ` Duncan [this message]
2008-09-29 6:40 ` Zac Medico
2008-09-29 11:52 ` Duncan
2008-09-29 6:04 ` [gentoo-dev] " Rémi Cardona
2008-09-29 6:33 ` Zac Medico
2008-09-29 19:52 ` [gentoo-dev] " Steve Long
2008-09-29 20:28 ` Zac Medico
2008-09-29 20:42 ` [gentoo-dev] " Steve Long
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.2008.09.29.02.52.08@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@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