From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] version/slot locked dependencies in eclasses like autotools.eclass and vala.eclass
Date: Mon, 22 Jan 2018 11:37:28 -0500 [thread overview]
Message-ID: <CAJ0EP41c+5xFn4Lkes-hYH5p+X99+b4ai5Mf=qNRCkCH9s9xmQ@mail.gmail.com> (raw)
In-Reply-To: <ddf17880-6fe3-2762-f4e9-e8935c654d8f@gentoo.org>
On Sun, Jan 21, 2018 at 11:57 PM, Michael Orlitzky <mjo@gentoo.org> wrote:
> On 01/21/2018 11:24 PM, Zac Medico wrote:
>>
>> Some eclasses like autotools.eclass and vala.eclass generate
>> version/slot locked dependencies that cause the dependencies of
>> inheriting ebuilds to change when the versions in the eclasses are
>> updated. If possible, it would be nice to avoid this version/slot
>> locking. If not possible, then what should be do?
>>
>
> This changes the deps in stable ebuilds, and was already a no-no.
>
> If the dependencies are to remain in the eclasses, then the eclasses
> should get a new revision when those dependencies change. Afterwards,
> the consumers can be revbumped and stabilized normally to utilize the
> new eclass.
While that sounds like the right thing to do in theory, updating all
consumers of autotools.eclass whenever a new version of automake is
stabilized is really a lot of work for very little benefit.
next prev parent reply other threads:[~2018-01-22 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 4:24 [gentoo-dev] version/slot locked dependencies in eclasses like autotools.eclass and vala.eclass Zac Medico
2018-01-22 4:57 ` Michael Orlitzky
2018-01-22 6:20 ` Zac Medico
2018-01-22 10:10 ` [gentoo-dev] " Duncan
2018-01-22 15:04 ` Michael Orlitzky
2018-01-23 0:57 ` Duncan
2018-01-22 16:37 ` Mike Gilbert [this message]
2018-01-22 17:34 ` [gentoo-dev] " Michael Orlitzky
2018-01-23 3:17 ` Mike Gilbert
2018-01-22 13:14 ` Mart Raudsepp
2018-01-22 20:07 ` Zac Medico
2018-01-23 9:06 ` Mart Raudsepp
2018-01-24 2:36 ` Zac Medico
2018-01-22 16:57 ` Michał Górny
2018-01-22 17:17 ` Rich Freeman
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='CAJ0EP41c+5xFn4Lkes-hYH5p+X99+b4ai5Mf=qNRCkCH9s9xmQ@mail.gmail.com' \
--to=floppym@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