From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] News Item: Portage Dynamic Deps
Date: Mon, 22 Jan 2018 11:43:41 -0500 [thread overview]
Message-ID: <bfe914e1-dbf4-b926-94b7-befc0dd95f34@gentoo.org> (raw)
In-Reply-To: <1710293.ao4jWK1sT1@pinacolada>
[-- Attachment #1.1: Type: text/plain, Size: 1005 bytes --]
On 2018-01-22 05:28 AM, Andreas K. Huettel wrote:
> Am Montag, 22. Januar 2018, 08:01:08 CET schrieb Zac Medico:
>>
>> According to Gentoo policy, future ebuild dependency changes need to be
>> accompanied by a revision bump in order to trigger rebuilds for users.
>> Therefore, you should only need to use --changed-deps=y for a single
>> deep @world update. After that, if you encounter installed packages with
>> outdated dependencies in a future deep @world update, then you should
>> report it as a bug.
>
> Did you come up with a solution how to handle eclass-generated dependency
> changes then?
>
> I'd loathe to have to do identical revision bumps for, say, all perl-
> module.eclass consumers...
>
Based on what I'm seeing in perl-module.eclass now I don't think this
is an issue -- first, perl isn't slotted; second, perl doesn't specify
${PV} information in the eclass. If it started to do either of these,
then yes revbumps are going to start being necessary..
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 248 bytes --]
next prev parent reply other threads:[~2018-01-22 16:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 7:01 [gentoo-dev] News Item: Portage Dynamic Deps Zac Medico
2018-01-22 8:24 ` Alexis Ballier
2018-01-24 20:48 ` Zac Medico
2018-01-22 9:38 ` Dirkjan Ochtman
2018-01-24 20:53 ` Zac Medico
2018-01-22 10:28 ` Andreas K. Huettel
2018-01-22 10:53 ` James Le Cuirot
2018-01-22 16:43 ` Ian Stakenvicius [this message]
2018-01-22 16:45 ` Ciaran McCreesh
2018-01-24 7:05 ` Kent Fredric
2018-01-22 16:59 ` Michał Górny
2018-01-23 12:40 ` [gentoo-dev] " Michael Palimaka
2018-01-23 13:10 ` Rich Freeman
2018-01-23 13:15 ` Michael Orlitzky
2018-01-23 13:40 ` Michael Palimaka
2018-01-23 17:12 ` Rich Freeman
2018-01-24 10:31 ` Martin Vaeth
2018-01-24 11:16 ` Ulrich Mueller
2018-01-24 12:36 ` Martin Vaeth
2018-01-24 16:36 ` Ulrich Mueller
2018-01-24 20:58 ` [gentoo-dev] " 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=bfe914e1-dbf4-b926-94b7-befc0dd95f34@gentoo.org \
--to=axs@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