public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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 14:39:39 -0500	[thread overview]
Message-ID: <CAGfcS_=Y5hwaVw60cX==XxYPu0Z6wK5TOJYQrkc9Att83fqiHg@mail.gmail.com> (raw)
In-Reply-To: <21156.50471.613516.395616@a1i15.kph.uni-mainz.de>

On Sun, Dec 8, 2013 at 2:14 PM, Ulrich Mueller <ulm@gentoo.org> wrote:
>
> PMS just provides a mechanism, but doesn't prefer one SLOT value over
> another. Such a change would introduce policy into PMS which is not
> the right way to go.

Sure it does - it defaults to :* when :* was never specified. I don't
see how defaulting to :0= is a "policy" any more than :* is.

>
> If a dependency on a specific SLOT value is needed then it should be
> explicitly specified in the ebuild.

Honestly, I think this is kind of like saying that garbage collection
is useless because programmers should just correctly free anything
they create exactly once.

If maintainers were generally giving careful thought to slots in
dependencies then we wouldn't have packages that stick the slot in the
package name instead.  Sure, we can just ban packages like these and
force everybody to fix all the breakage that results (which in theory
should never have existed), but it seems better to me to try to make
the best default the default.

I guess we could just ban any non-explicit slot version dependency (ie
90% of our current dependency atoms are now invalid), but that doesn't
really seems a bit like programming in Ada.  :)

Rich


  reply	other threads:[~2013-12-08 19:39 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 [this message]
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_=Y5hwaVw60cX==XxYPu0Z6wK5TOJYQrkc9Att83fqiHg@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