| 1 |
Another point that is directly related (and a good reason to first |
| 2 |
check'/var/db/pkg/virtual/...') is that the jdk provides the jre as |
| 3 |
well. The jdk package properly records this in |
| 4 |
'/var/db/pkg/virtual/jre-*/VIRTUAL', but updating doesn't respect this. |
| 5 |
I have the blackdown jdk installed, for example, but when doing a world |
| 6 |
update, I am always prompted to install the jre as well. |
| 7 |
|
| 8 |
I do think this is a bug. Would you care to report it? |
| 9 |
|
| 10 |
Zach |
| 11 |
|
| 12 |
Defresne Sylvain wrote: |
| 13 |
> * Ric Messier (kilroy@×××××××.COM) wrote: |
| 14 |
> |
| 15 |
>>Nope. Just checked. I removed java-config. I then did an emerge |
| 16 |
>>--pretend --world update and I get the following: |
| 17 |
>> |
| 18 |
>>[ebuild U] app-shells/sash-3.4-r5 to / |
| 19 |
>>[ebuild U] sys-apps/sh-utils-2.0.11-r2 to / |
| 20 |
>>[ebuild U] sys-devel/spython-2.0-r9 to / |
| 21 |
>>[ebuild U] x11-base/xfree-4.2.0-r8 to / |
| 22 |
>>[ebuild N ] dev-java/java-config-0.1.3 to / |
| 23 |
>>[ebuild N ] dev-java/blackdown-jre-1.3.1-r4 to / |
| 24 |
>>[ebuild U] app-games/dopewars-1.5.4 to / |
| 25 |
>>[ebuild N ] dev-java/blackdown-jdk-1.3.1-r2 to / |
| 26 |
>>[ebuild U] gnome-base/gnome-mime-data-1.0.1-r1 to / |
| 27 |
>>[ebuild U] x11-libs/gtk+-1.2.10-r6 to / |
| 28 |
>>[ebuild U] gnome-base/eel-1.0.2-r1 to / |
| 29 |
>>[ebuild U] gnome-base/gnome-core-1.4.0.6-r2 to / |
| 30 |
>>[ebuild U] gnome-extra/medusa-0.5.1-r3 to / |
| 31 |
>>[ebuild U] app-admin/syslog-ng-1.4.12-r8 to / |
| 32 |
>> |
| 33 |
>>You will notice that it wants to install blackdown and java-config as |
| 34 |
>>new packages. This seems broken. If I remove them, they shouldn't be in |
| 35 |
>>the list to be updated (or re-installed). Is this a bug or am I missing |
| 36 |
>>something? If it's a bug, I'll submit it. |
| 37 |
> |
| 38 |
> |
| 39 |
> Does any of your installed application depends on 'virtual/jdk' (or |
| 40 |
> 'virtual/jre'). If this is the case, it will explain why 'blackdown' |
| 41 |
> version of java is reinstalled each time you do an 'emerge --world'. |
| 42 |
> |
| 43 |
> When searching for a package providing 'virtual/jdk', portage first look |
| 44 |
> in '/etc/make.profile/virtuals' and find 'dev-java/blackdown-jdk' and so |
| 45 |
> it wants to install it. |
| 46 |
> |
| 47 |
> I see it as a bug in how portage decides which package provide a |
| 48 |
> 'virtual' package. In the current implementation (1.8.8 for me), it |
| 49 |
> first look in '/etc/make.profile/virtual' and if no package if found |
| 50 |
> it search in the database of installed package. |
| 51 |
> |
| 52 |
> I think that it should first look in '/var/db/pkg/virtual/...', and |
| 53 |
> only if no package is found uses '/etc/make.profile/virtuals' as a |
| 54 |
> fallback. With such a scheme, '/etc/make.profile/virtuals' would be |
| 55 |
> used as a list of default 'virtual' package provider, but can be |
| 56 |
> overriden by locally installed package. |
| 57 |
> |
| 58 |
> I think I'll submit this as a bug in portage soon unless someone |
| 59 |
> involved in portage developpement say this is not a bug but the intended |
| 60 |
> behaviour |
| 61 |
> |
| 62 |
> As a workaround, you can edit '/etc/make.profile/virtuals' and replace |
| 63 |
> 'dev-java/blackdown-jdk' by 'dev-java/sun-jdk' (and also for '*-jre'). |
| 64 |
> |
| 65 |
> Bye |
Archives