public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] version/slot locked dependencies in eclasses like autotools.eclass and vala.eclass
Date: Sun, 21 Jan 2018 23:57:43 -0500	[thread overview]
Message-ID: <ddf17880-6fe3-2762-f4e9-e8935c654d8f@gentoo.org> (raw)
In-Reply-To: <c0158b91-cd7f-9a20-e479-1c9871e48695@gentoo.org>

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.



> Should we tell users to use the emerge --changed-deps=y option? Maybe
> make --changed-deps=y a default setting?
> 

Our tree shouldn't require a portage-only option to work. Besides, it's
better engineering to have the one person who makes the change alert the
rest of us. Having a million people poll "Did somebody change this? How
about now?" constantly is silly.


  reply	other threads:[~2018-01-22  4:57 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 [this message]
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   ` [gentoo-dev] " Mike Gilbert
2018-01-22 17:34     ` 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=ddf17880-6fe3-2762-f4e9-e8935c654d8f@gentoo.org \
    --to=mjo@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