On Sunday 01 January 2006 02:39, Holly Bostick wrote: > And iirc, the virtual is not going to be linked to a hard-masked package > (or at least it most likely is not atm, or the hard-masked packages are > listed after the stable packages). > > So what I would do is check /var/cache/edb/virtuals and see what the > listing for jdk actually is.
Ok, you're right off the track here. /var/cache/edb/virtuals hasn't been used (at all) since 2.0.50. Packages that provide virtuals are looked up when emerge is run and the internal list of those is essentially arbitrary. Virtuals listed in /etc/make.profile (and parents) are put after those in correct order. Virtuals listed in /etc/portage/profile/virtuals are put at the front. When there is a virtual dependency, these are checked in order for the first unmasked package that is able to satisfy the dependency. The fact that sun-jdk is being chosen means that it is the first package to have any unmasked versions available from the internal list. sun-jdk-1.4* being chosen means that sun-jdk-1.5* is still masked. sun-jdk-1.5* is in package.mask so adding dev-java/sun-jdk (or even =dev-java/sun-jdk-1.5*) to /etc/portage/package.unmask should fix that issue. It also has a KEYWORDS of "~x86 ~amd64" so adding the same to /etc/portage/package.keywords should fix that issue. Beyond that there shouldn't be a problem. -- Jason Stubbs -- gentoo-user@gentoo.org mailing list
