| 1 |
Jason Stubbs schreef: |
| 2 |
> On Saturday 31 December 2005 21:57, Holly Bostick wrote: |
| 3 |
> |
| 4 |
>> If you look at the output |
| 5 |
>> |
| 6 |
>> |
| 7 |
>>> [nomerge ] sys-libs/db-4.2.52_p2-r1 -bootstrap +doc |
| 8 |
>>> +java -nocxx +tcltk |
| 9 |
>> |
| 10 |
>> the reason db is calling for java is because you have the "java" |
| 11 |
>> USE flag set for db. |
| 12 |
>> |
| 13 |
>> Do you really need db to use Java? If not, disable the flag (# echo |
| 14 |
>> 'sys-libs/db -java' >>/etc/portage/package.use); problem solved. |
| 15 |
> |
| 16 |
> |
| 17 |
> All the way up until the next package which depends on java. Only the |
| 18 |
> first package that is came across is listed as the parent. |
| 19 |
> sys-libs/db doesn't call for any specific version of java. The |
| 20 |
> complaint is that sun-jdk-1.5 is installed but emerge is wanting to |
| 21 |
> install sun-jdk-1.4. This indicates that sun-jdk-1.5 is likely |
| 22 |
> masked. |
| 23 |
> |
| 24 |
|
| 25 |
Well that's all true, Jason, but my point was that this is an *option*, |
| 26 |
not a hard dependency, and many times people have USE flags enabled for |
| 27 |
things they don't even need (or need for the specific program). |
| 28 |
|
| 29 |
So Kevin certainly could unmask sun-jdk 1.5 --and if it's installed, then |
| 30 |
how did that happen without it being unmasked? Sun-jdk-1.5 is |
| 31 |
hard-masked! The original post does not say that any version of the jdk |
| 32 |
is actually installed: |
| 33 |
|
| 34 |
> Anyway, my latest emerge world failed because of sun-jdk-1.4.2.10 |
| 35 |
> (!!!). The current one is 1.5 something. |
| 36 |
|
| 37 |
Meaning (to me) that Kevin is referring to the current *available* |
| 38 |
*version* of sun-jdk, not to any version he might have installed (and my |
| 39 |
impression is that he does not in fact have any version of sun-jdk |
| 40 |
installed), and he's just concerned that an "out-of-date" version will |
| 41 |
be installed rather than the latest. |
| 42 |
|
| 43 |
But if he doesn't need java support in the db at all, then disabling the |
| 44 |
USE flag entirely (globally or for this package alone), then java won't |
| 45 |
be called by the emerge of db, which saves having to unmask a package |
| 46 |
that Kevin may have concerns about installing in the first place if he |
| 47 |
runs stable, or even unstable-- sun-jdk-1.5 *is* hard-masked, after all, |
| 48 |
and one should rightfully think twice and then think again about |
| 49 |
installing a hard-masked package-- and secondly does not install bloat |
| 50 |
onto the system (if he doesn't need java support in db, then he has no |
| 51 |
reason to install it, or spend the extra compile time installing db java |
| 52 |
support). |
| 53 |
|
| 54 |
I've often solved similar issues on my own system by the simple |
| 55 |
expedient of disabling the USE flag that was calling the dependency that |
| 56 |
was giving me a problem. Helps keep the system clean. |
| 57 |
|
| 58 |
Holly |
| 59 |
-- |
| 60 |
gentoo-user@g.o mailing list |
Archives