| 1 |
Hi, |
| 2 |
|
| 3 |
I have an annoying bug, caused by a portage deficiency that imho can be |
| 4 |
quite easily solved: |
| 5 |
|
| 6 |
Assume the virtual/jdk is satisfied by blackdown-jdk with version-1.3 |
| 7 |
(meaning: blackdown-jdk-1.3 is installed and provides virtual/jdk-1.3) |
| 8 |
The virtual/jdk default implementation is then changed from |
| 9 |
blackdown-jdk to ibm-jdk in the users profile. |
| 10 |
The user installs a package depending on virtual/jdk-1.4, ibm-jdk with |
| 11 |
version 1.4 gets installed. |
| 12 |
|
| 13 |
When the user runs emerge --update world, portage complains there is no |
| 14 |
1.4 version of blackdown-jdk. |
| 15 |
|
| 16 |
To make emerge --update world work again, the user has to unmerge |
| 17 |
blackdown-jdk. If the user emerges blackdown-jdk again afterwards, |
| 18 |
emerge --update world still works. |
| 19 |
Shouldn't portage update the virtual provider every time an ebuild |
| 20 |
providing a virtual gets installed? |
| 21 |
|
| 22 |
Best regards, |
| 23 |
|
| 24 |
Pieter Van den Abeele |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-portage-dev@g.o mailing list |
Archives