From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Dependencies default to accept any slot value acceptable (:*), can we default to :0 instead?
Date: Sun, 8 Dec 2013 21:55:59 -0500 [thread overview]
Message-ID: <CAGfcS_nOBptt5MifpFXrrRnHyYwVxH-EK9Z2ujkaA2Bb6+4Yzw@mail.gmail.com> (raw)
In-Reply-To: <86wqjeu4vf.fsf@moguhome00.in.awa.tohoku.ac.jp>
On Sun, Dec 8, 2013 at 9:37 PM, <heroxbd@gentoo.org> wrote:
>
> How about defining a QA workflow for introducing a new slot of a
> library, such as "mask it and open a tracker bug until every individual
> reverse dependencies are checked"?
>
The problem with this is that it puts the onus on the person who wants
to make forward progress (adding support for a new library version).
That means that they have incentive to either not bother with the new
library version (causing Gentoo to stagnate), or use hacks like giving
the library a new name (which we have examples in the tree of).
Now, perhaps a more balanced approach might be to mask it and give 15
days notice on -dev, and then it can be unmasked. Anybody who cares
about the library can test the new version, and if necessary update
their dependencies to use the previous slot only (and if 15 days isn't
enough time they can just update the dep right away and then update it
again after they get around to testing it). Those who don't want to
have to deal with that can just define their slot dependencies
explicitly so that this policy will never apply to them.
In order for a QA policy to be effective it has to either be minimally
intrusive, or make the cost of compliance lower than the cost of
workarounds or benign neglect. People don't HAVE to maintain
packages, after all...
Rich
next prev parent reply other threads:[~2013-12-09 2:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 16:56 [gentoo-dev] Dependencies default to accept any slot value acceptable (:*), can we default to :0 instead? Tom Wijsman
2013-12-08 17:16 ` Michał Górny
2013-12-08 17:19 ` Andreas K. Huettel
2013-12-08 17:26 ` Pacho Ramos
2013-12-08 17:46 ` Tom Wijsman
2013-12-08 18:56 ` Rich Freeman
2013-12-08 19:14 ` Ulrich Mueller
2013-12-08 19:39 ` Rich Freeman
2013-12-08 19:48 ` Ciaran McCreesh
2013-12-08 20:01 ` Ulrich Mueller
2013-12-08 20:17 ` Rich Freeman
2013-12-09 2:37 ` heroxbd
2013-12-09 2:55 ` Rich Freeman [this message]
2013-12-09 3:19 ` heroxbd
2013-12-08 20:21 ` Tom Wijsman
2013-12-08 20:25 ` Ciaran McCreesh
2013-12-10 21:06 ` Ian Stakenvicius
2013-12-10 23:35 ` Tom Wijsman
2013-12-08 20:04 ` Tom Wijsman
2013-12-08 20:21 ` Ulrich Mueller
2013-12-08 20:26 ` Ciaran McCreesh
2013-12-08 20:31 ` Ulrich Mueller
2013-12-08 21:54 ` Michał Górny
2013-12-08 22:02 ` Ciaran McCreesh
2013-12-08 20:28 ` Tom Wijsman
2013-12-08 20:30 ` Tom Wijsman
-- strict thread matches above, loose matches on Subject: below --
2013-12-08 16:54 Tom Wijsman
2013-12-08 23:57 ` Patrick Lauer
2013-12-09 0:12 ` Tom Wijsman
2013-12-09 0:21 ` Rich Freeman
2013-12-09 6:52 ` Sergey Popov
2013-12-09 10:55 ` Tom Wijsman
2013-12-09 16:06 ` Rich Freeman
2013-12-09 16:19 ` Ulrich Mueller
2013-12-10 0:31 ` Tom Wijsman
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=CAGfcS_nOBptt5MifpFXrrRnHyYwVxH-EK9Z2ujkaA2Bb6+4Yzw@mail.gmail.com \
--to=rich0@gentoo.org \
--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