From: Pacho Ramos <pacho@gentoo.org>
To: 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, 08 Dec 2013 18:26:25 +0100 [thread overview]
Message-ID: <1386523585.12112.5.camel@belkin5> (raw)
In-Reply-To: <201312081819.40449.dilfridge@gentoo.org>
El dom, 08-12-2013 a las 18:19 +0100, Andreas K. Huettel escribió:
> Am Sonntag, 8. Dezember 2013, 17:56:12 schrieb Tom Wijsman:
> >
> > When our defaults force us down such path, that can't be good and it
> > affects the quality of our Portage tree; so, this makes me wonder, can
> > we change the default from :* to :0? What do you think?
> >
>
> I see the point, but I have my doubts on retroactively changing things.
> (It's a global change where we would have to be very very very careful
> regarding interactions with eclasses and so on.)
>
> How about changing this in the next EAPI instead?
>
> E.g., in EAPI=6, if no slot dependency is given in a dependency specification,
> default to :0
>
> --
>
> Andreas K. Huettel
> Gentoo Linux developer
> dilfridge@gentoo.org
> http://www.akhuettel.de/
>
Other option I have sometimes consider is to force people to specify the
slot dependency on a newer eapi -> if a package is working for any slot,
specify :*, if not, specify the slot that it needs. That way, this kind
of problems would be much less frequent than currently
next prev parent reply other threads:[~2013-12-08 17:26 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 [this message]
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
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=1386523585.12112.5.camel@belkin5 \
--to=pacho@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