Summary: | sys-apps/portage-2.1.9.25 : slotted RDEPEND behavior is no longer preserving two versions | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Robert Forsman <gentoo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | darkside, serkan |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robert Forsman
2011-01-27 19:48:11 UTC
Why don't you just add the SLOT you want to your world file? That way depclean won't remove the SLOTed version because you have stated that you EXPLICITLY want it. emerge --noreplace gentoo-sources:2.6.29-r5 You could change your ebuild to
RDEPEND="
=sys-kernel/gentoo-sources-2.6.29-r5
>=sys-kernel/gentoo-sources-2.6.30
!>sys-fs/udev-164
"
I guess the behavior change comes from bug 285767, in this commit: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=51140af8783fae99ff2b2f5ca5f45bcfeb689b91 The new behavior should be preferable to the old, so I agree with the suggestion in comment #2. (In reply to comment #1) > Why don't you just add the SLOT you want to your world file? That way depclean > won't remove the SLOTed version because you have stated that you EXPLICITLY > want it. Well, I don't think they had that syntax when I first figured out this method using ebuilds. Also, I suspect that if I had gentoo-sources and gentoo-sources:2.6.29-r5 in /var/lib/portage/world then it would never unmerge the stale gentoo-sources. I haven't studied the enhancements to the world file that might make it possible to express "only the most recent of this slotted build". Perhaps my old syntax working the way I wanted was just a historical accident. I can see why the fix referenced in comment #3 would affect me, and agree that its behavior is probably preferrable. The solution in comment #2 would work, assuming there is a more recent version of gentoo-sources. There's just an awkward phase where I transition to the latest kernel. What would the ebuild look like (since there wouldn't be anything more recent, the atom would lead to a failure?) (In reply to comment #4) > Also, I suspect that if I had gentoo-sources and gentoo-sources:2.6.29-r5 in > /var/lib/portage/world then it would never unmerge the stale gentoo-sources. I > haven't studied the enhancements to the world file that might make it possible > to express "only the most recent of this slotted build". It should work, since world atoms are not greedy. That's why we have (unsolved) bug 198200, since some people want to keep "stale gentoo-sources" and don't want to manage it via non-greedy atoms in the world file. |