Re: [gentoo-dev] emerge --world update

[Zach Forrest <zach@disinformation.ca>]

  Another point that is directly related (and a good reason to first 
check'/var/db/pkg/virtual/...') is that the jdk provides the jre as 
well. The jdk package properly records this in 
'/var/db/pkg/virtual/jre-*/VIRTUAL', but updating doesn't respect this. 
I have the blackdown jdk installed, for example, but when doing a world 
update, I am always prompted to install the jre as well.

I do think this is a bug. Would you care to report it?

Zach

Defresne Sylvain wrote:
> * Ric Messier (kilroy@WasHere.COM) wrote:
> 
>>Nope. Just checked. I removed java-config. I then did an emerge
>>--pretend --world update and I get the following:
>>
>>[ebuild   U] app-shells/sash-3.4-r5 to /
>>[ebuild   U] sys-apps/sh-utils-2.0.11-r2 to /
>>[ebuild   U] sys-devel/spython-2.0-r9 to /
>>[ebuild   U] x11-base/xfree-4.2.0-r8 to /
>>[ebuild N  ] dev-java/java-config-0.1.3 to /
>>[ebuild N  ] dev-java/blackdown-jre-1.3.1-r4 to /
>>[ebuild   U] app-games/dopewars-1.5.4 to /
>>[ebuild N  ] dev-java/blackdown-jdk-1.3.1-r2 to /
>>[ebuild   U] gnome-base/gnome-mime-data-1.0.1-r1 to /
>>[ebuild   U] x11-libs/gtk+-1.2.10-r6 to /
>>[ebuild   U] gnome-base/eel-1.0.2-r1 to /
>>[ebuild   U] gnome-base/gnome-core-1.4.0.6-r2 to /
>>[ebuild   U] gnome-extra/medusa-0.5.1-r3 to /
>>[ebuild   U] app-admin/syslog-ng-1.4.12-r8 to /
>>
>>You will notice that it wants to install blackdown and java-config as
>>new packages. This seems broken. If I remove them, they shouldn't be in
>>the list to be updated (or re-installed). Is this a bug or am I missing
>>something? If it's a bug, I'll submit it.
> 
> 
>   Does any of your installed application depends on 'virtual/jdk' (or
> 'virtual/jre'). If this is the case, it will explain why 'blackdown'
> version of java is reinstalled each time you do an 'emerge --world'.
> 
>   When searching for a package providing 'virtual/jdk', portage first look
> in '/etc/make.profile/virtuals' and find 'dev-java/blackdown-jdk' and so
> it wants to install it.
> 
>   I see it as a bug in how portage decides which package provide a
> 'virtual' package. In the current implementation (1.8.8 for me), it
> first look in '/etc/make.profile/virtual' and if no package if found
> it search in the database of installed package.
> 
>   I think that it should first look in '/var/db/pkg/virtual/...', and
> only if no package is found uses '/etc/make.profile/virtuals' as a
> fallback. With such a scheme, '/etc/make.profile/virtuals' would be
> used as a list of default 'virtual' package provider, but can be
> overriden by locally installed package.
> 
>   I think I'll submit this as a bug in portage soon unless someone
> involved in portage developpement say this is not a bug but the intended
> behaviour
> 
>   As a workaround, you can edit '/etc/make.profile/virtuals' and replace
> 'dev-java/blackdown-jdk' by 'dev-java/sun-jdk' (and also for '*-jre').
> 
> Bye