[gentoo-portage-dev] virtual evolution

[gentoo-portage-dev] virtual evolution

[Pieter Van den Abeele]

Hi,

I have an annoying bug, caused by a portage deficiency that imho can be 
quite easily solved:

Assume the virtual/jdk is satisfied by blackdown-jdk with version-1.3 
(meaning: blackdown-jdk-1.3 is installed and provides virtual/jdk-1.3)
The virtual/jdk default implementation is then changed from 
blackdown-jdk to ibm-jdk in the users profile.
The user installs a package depending on virtual/jdk-1.4, ibm-jdk with 
version 1.4 gets installed.

When the user runs emerge --update world, portage complains there is no 
1.4 version of blackdown-jdk.

To make emerge --update world work again, the user has to unmerge 
blackdown-jdk. If the user emerges blackdown-jdk again afterwards, 
emerge --update world still works.
Shouldn't portage update the virtual provider every time an ebuild 
providing a virtual gets installed?

Best regards,

Pieter Van den Abeele


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] virtual evolution

[Paul de Vrieze]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 06 May 2004 03:24, Pieter Van den Abeele wrote:

> To make emerge --update world work again, the user has to unmerge
> blackdown-jdk. If the user emerges blackdown-jdk again afterwards,
> emerge --update world still works.
> Shouldn't portage update the virtual provider every time an ebuild
> providing a virtual gets installed?

I don't know. In any case the provider should be a default, not the only 
option. That means that when the default provider is not available for 
this version, it should find another one that is.

Paul

- -- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAmggTbKx5DBjWFdsRAvKSAJ9+ARYbYkOMNyUxOUWn0fVW4721WwCghjRY
ONiEhOnOgdpu8kUUTc9X7pE=
=CfR3
-----END PGP SIGNATURE-----

--
gentoo-portage-dev@gentoo.org mailing list