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