339144 – Old style virtuals are higher priority than new style

Bug 339144 - Old style virtuals are higher priority than new style

Summary: Old style virtuals are higher priority than new style

Status:	RESOLVED INVALID

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Dependencies (show other bugs)
Hardware:	All Linux

Importance:	High normal
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-09-29 16:27 UTC by Radoslaw Szkodzinski
Modified:	2011-05-12 19:54 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Radoslaw Szkodzinski 2010-09-29 16:27:57 UTC

I've found this issue while trying to merge a new style virtual.
Suppose we have an old virtual package app-crypt/mit-krb5, which has
PROVIDES="virtual/krb5"

Now I created a new /usr/local/portage/virtual/krb5/krb5-0.ebuild, which contains
RDEPEND="|| ( app-crypt/heimdal app-crypt/mit-krb5 )"

Unfortunately, this is the result of trying to merge it:
[ebuild  N    ] virtual/krb5-0  0 kB [0=>1]
[blocks B     ] app-crypt/mit-krb5 ("virtual/krb5" is blocking app-crypt/mit-krb5-1.8.3)

Comment 1 Radoslaw Szkodzinski 2010-09-29 16:28:51 UTC

Forgot this:
Portage 2.2_rc88 (hardened/linux/amd64/10.0, gcc-4.4.4, glibc-2.12.1-r0, 2.6.35-ck1+ x86_64)

Comment 2 Zac Medico gentoo-dev

2010-09-29 16:47:29 UTC

It's not a matter of "priority". What you're trying to do would work perfectly fine if you removed the blocker from the mit-krb5-1.8.3 ebuild. If you're transitioning to new-style virtuals then that blocker doesn't make sense anyway. Given the blocker, portage is behaving correctly. It wouldn't be right for portage to ignore the blocker.