From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: revbumping ebuilds after USE dependency changes
Date: Wed, 24 Jul 2013 20:44:12 +0100 [thread overview]
Message-ID: <20130724204412.6f8c094a@googlemail.com> (raw)
In-Reply-To: <20130724134048.32732b45@caribou.gateway.2wire.net>
[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]
On Wed, 24 Jul 2013 13:40:48 -0600
Ryan Hill <dirtyepic@gentoo.org> wrote:
> > Actually per PMS you are required to revbump (and therefore require
> > upgrade on users' side) whenever you change the deps and don't
> > expect to add a new version soon enough. Otherwise your changes
> > don't get spread and users end up with never-ending blockers and
> > stuff like that.
> >
> > Other thing is that Portage explicitly ignores PMS in this matter
> > and uses dependencies from ebuilds rather than recorded ones. This
> > is supposedly wrong, supposedly slow but allows us to be lazy.
>
> Thank god. That is insane.
>
> Let's not document that one in the manual.
The issue's not as simple as one might initially think, and both ways
have their drawbacks.
The only drawback of "use dependencies at the time the package was
installed" is that developers can't retroactively change dependencies
without a revbump.
The drawbacks of "use VDB" are:
* That ebuilds can be updated without revbumps to have "changed"
dependencies. The example that comes up most is pkg_prerm changes to
use or stop using a foo-config type app. If a package mangler then
uses the "changed" dependencies, it can lead to premature
uninstallation of a foo-config that's needed to safely uninstall
something.
* That it assumes there's a one-to-one correspondence between
"installed ebuild" and "installable ebuild". This means that whenever
ebuild versions are cleaned up in the tree, suddenly the dependencies
of your installed packages change. It gets even trickier when
overlays and binaries are involved.
* The way Portage does it doesn't work if there are := dependencies.
So the tradeoff is between "require more revbumps" or "randomly broken
dependency handling", and neither is ideal. Portage currently leans
towards the latter, on the grounds that users expect broken
dependencies and strange failures every now and again, but hate
"wasting time" on "unnecessary" revbumps.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-07-24 19:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 12:49 [gentoo-dev] revbumping ebuilds after USE dependency changes Alex Alexander
[not found] ` < CAJ0EP43edWPPYXXMOQPL4V2ZdO8R4YArpcNJK5cgBOqahzVdYw@mail.gmail.com>
2013-07-24 14:15 ` Mike Gilbert
2013-07-24 15:31 ` Alex Alexander
2013-07-24 15:48 ` "Paweł Hajdan, Jr."
[not found] ` < 20130724132315.19acde44@caribou.gateway.2wire.net>
2013-07-24 19:23 ` [gentoo-dev] " Ryan Hill
2013-07-24 19:17 ` Michał Górny
2013-07-24 19:18 ` Ciaran McCreesh
2013-07-25 0:53 ` Rick "Zero_Chaos" Farina
2013-07-25 3:50 ` "Paweł Hajdan, Jr."
2013-07-25 3:54 ` Zac Medico
2013-07-25 15:29 ` Rick "Zero_Chaos" Farina
2013-07-25 17:28 ` Zac Medico
2013-07-25 18:29 ` Rick "Zero_Chaos" Farina
2013-07-25 18:36 ` Zac Medico
2013-07-24 19:40 ` Ryan Hill
2013-07-24 19:44 ` Ciaran McCreesh [this message]
2013-07-25 7:07 ` Michael Palimaka
2013-07-28 9:11 ` Michał Górny
2013-07-28 12:37 ` Kent Fredric
[not found] ` <20130728111113.318cdc6a@gentoo. org>
2013-07-29 0:39 ` Duncan
2013-07-29 8:04 ` Zac Medico
2013-07-29 11:03 ` Duncan
2013-07-24 17:54 ` [gentoo-dev] " Davide Pesavento
2013-07-25 7:43 ` Dale
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=20130724204412.6f8c094a@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--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