1 |
On Thursday 05 April 2007, Marc Blumentritt wrote: |
2 |
> Thanks for the answers, but to be honest, I still do not get, what |
3 |
> the problem is and how to solve it. Could someone explain me, what |
4 |
> goes wrong, if I use a binary package like sun-jdk? |
5 |
|
6 |
The problem is that you can't recompile sun-jdk. |
7 |
|
8 |
Say you have package A which needs library B. You update library B to |
9 |
the next higher version, but neither library B nor it's ebuild is aware |
10 |
of other packages that use or may use it. Don't try and "fix" this - |
11 |
there be dragons... |
12 |
|
13 |
revdep-rebuild might now detect that binary files in package A are still |
14 |
looking for old libs that have been replaced in the meantime. The |
15 |
solution is easy - recompile package A and the build process will find |
16 |
and link to the correct libraries that you now *do* have. But you can't |
17 |
do that with a third party binary app. |
18 |
|
19 |
Remember that ebuild defines which *packages* they depend on, not the |
20 |
files in those packages. So it's quite possible that sun compiled |
21 |
something that would like to use lib-1.2.3.so and you have |
22 |
lib-1.2.5.so. It all still works nicely because the shared libraries |
23 |
system is designed to cope with this as an essential feature, but |
24 |
revdep-rebuild will complain. |
25 |
|
26 |
You *could* get around the problem with a complex arrangment of |
27 |
symlinks, but then you'd have to maintain them. It's so much easier to |
28 |
just tell revdep-rebuild to ignore the binary package altogether, using |
29 |
Rumen and Neil's suggestions |
30 |
|
31 |
alan |
32 |
|
33 |
|
34 |
-- |
35 |
Optimists say the glass is half full, |
36 |
Pessimists say the glass is half empty, |
37 |
Developers say wtf is the glass twice as big as it needs to be? |
38 |
|
39 |
Alan McKinnon |
40 |
alan at linuxholdings dot co dot za |
41 |
+27 82, double three seven, one nine three five |
42 |
-- |
43 |
gentoo-user@g.o mailing list |