From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: On the good usage of subslots
Date: Sat, 9 Feb 2013 09:46:37 -0300 [thread overview]
Message-ID: <20130209094637.4cb02466@gentoo.org> (raw)
In-Reply-To: <kf5g08$ns1$1@ger.gmane.org>
On Sat, 09 Feb 2013 23:38:35 +1100
Michael Palimaka <kensington@gentoo.org> wrote:
> Hi,
>
> On 9/02/2013 23:15, Alexis Ballier wrote:
> > Dear fellow developers,
> >
> > I hope this will be trivial to most of you but after seeing bug
> > #455900 and the vast majority of developers not even thinking twice
> > before sedding their dep strings, I believe this needs some
> > attention.
>
> What is wrong with maintainers just updating their dependencies in
> this fashion? Surely the onus in this case is on package maintainers
> setting sensible subslots (which is indeed what you appear to be
> saying below)?
If subslot does not represent ABI then it's wrong to set such := deps:
By setting them you are forcing your users to needlessly rebuild your
package.
Think about glib: gobject-introspection needs to be rebuilt after each
glib update. glib maintainers will likely want glib to have ${PV} as
subslot and let gobject-introspection := depend on it. Packages that do
not break with minor updates of glib (ie 99% of them) should not :=
depend on glib, even if it has a subslot.
What I wanted to say could be summarized as: Please define what your
subslot means when you define one and please check if that is the
meaning you want to give it when you set := deps.
Alexis.
next prev parent reply other threads:[~2013-02-09 12:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 12:15 [gentoo-dev] On the good usage of subslots Alexis Ballier
2013-02-09 12:38 ` [gentoo-dev] " Michael Palimaka
2013-02-09 12:46 ` Alexis Ballier [this message]
2013-02-09 12:52 ` Alexis Ballier
2013-02-09 14:09 ` Michael Palimaka
2013-02-11 0:45 ` Alexis Ballier
2013-02-11 15:40 ` Ian Stakenvicius
2013-02-09 13:47 ` [gentoo-dev] " Samuli Suominen
2013-02-09 14:05 ` [gentoo-dev] " Michael Palimaka
2013-02-09 16:06 ` Zac Medico
2013-02-09 16:36 ` Michael Palimaka
2013-02-09 16:39 ` Samuli Suominen
2013-02-09 16:53 ` Pacho Ramos
2013-02-09 19:21 ` [gentoo-dev] " Michał Górny
2013-02-11 0:44 ` Alexis Ballier
2013-02-11 20:53 ` James Cloos
2013-02-11 21:13 ` Ian Stakenvicius
2013-02-11 21:21 ` Zac Medico
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=20130209094637.4cb02466@gentoo.org \
--to=aballier@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