public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Mart Raudsepp <leio@gentoo.org>
Subject: Re: [gentoo-dev] version/slot locked dependencies in eclasses like autotools.eclass and vala.eclass
Date: Mon, 22 Jan 2018 12:07:31 -0800	[thread overview]
Message-ID: <b4116668-b656-e0aa-37ff-d1a4625eb19b@gentoo.org> (raw)
In-Reply-To: <1516626863.9122.3.camel@gentoo.org>

On 01/22/2018 05:14 AM, Mart Raudsepp wrote:
> On Sun, 2018-01-21 at 20:24 -0800, Zac Medico wrote:
>> Hi,
>>
>> In sys-app/portage-2.3.20, emerge now defaults to --dynamic-deps=n.
>> This
>> means that unless people explicitly set
>> EMERGE_DEFAULT_OPTS="--dynamic-deps=y" they're going to have to
>> rebuild
>> packages any time that the runtime dependencies of those packages
>> need
>> to be updated. It's possible to trigger these rebuilds using the
>> emerge
>> --changed-deps=y option.
>>
>> 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?
> 
> These are mostly build time only depends, why should the user now all
> of a sudden care before an unrelated rebuild or upgrade, which would
> actually matter only then, not before?

For various reasons, current versions of portage enable the
--with-bdeps=y option by default [1]. Basically, failing to update
installed packages and possibly leaving them with broken dependencies is
not really a sane default behavior.

[1] https://bugs.gentoo.org/598444
-- 
Thanks,
Zac


  reply	other threads:[~2018-01-22 20:07 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   ` [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 [this message]
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=b4116668-b656-e0aa-37ff-d1a4625eb19b@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=leio@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