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 13:56:12 -0500 [thread overview]
Message-ID: <CAGfcS_nmvtzfy1MN+YiubkwK=Dh+U-fh-fmLi61enkNy2QtKLw@mail.gmail.com> (raw)
In-Reply-To: <20131208184654.664760b7@TOMWIJ-GENTOO>
On Sun, Dec 8, 2013 at 12:46 PM, Tom Wijsman <TomWij@gentoo.org> wrote:
>
> Given that the retroactive change I suggest causes a lot of complexity;
> changing it on the next EAPI indeed sounds like one way to go, the
> alternative is to make it a suggestive guideline or policy and cover
> it as a QA check in repoman.
>
> That QA check could throw a warning when a dependency has no slot.
I think we're better off with defaulting to slot 0 rather than
erroring/warning if no slot is specified. Otherwise we're basically
going to have to modify every ebuild in the tree to add the :0 (unless
there is no warning when only slot 0 exists, but then another slot
could be added at any time and what is the behavior then?).
Or we could do both - we could define EAPI 6 as having :0 be the
default slot behavior, and we could have repoman offer soft warnings
on earlier EAPIs if there is no explicit slot.
(I'd even suggest making the default :0= except that there is no way
to override that as we defined not depending on a subslot as the
absence of any operator and not a different operator that is simply
defaulted.)
Rich
next prev parent reply other threads:[~2013-12-08 18: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 [this message]
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
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_nmvtzfy1MN+YiubkwK=Dh+U-fh-fmLi61enkNy2QtKLw@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