1 |
On Sunday, August 28, 2011 14:38:31 Michael wrote: |
2 |
> Mike Frysinger wrote: |
3 |
> > like Nathan said, only if the package directly uses/links against the X11 |
4 |
> > API/libs in question. if the package only uses gtk+ funcs, then it |
5 |
> > should not be declaring a dependency on the X11 libs. |
6 |
> |
7 |
> Just to confirm (as I've had one such bug marked WONTFIX), should a package |
8 |
> that depends on say, qt-gui (which in turn depends on qt-core), list an |
9 |
> explicit dependency on qt-core if it uses symbols from it? |
10 |
> |
11 |
> tinderbox ~ # readelf -d /usr/bin/lfhex | grep Qt |
12 |
> 0x0000000000000001 (NEEDED) Shared library: [libQtGui.so.4] |
13 |
> 0x0000000000000001 (NEEDED) Shared library: [libQtCore.so.4] |
14 |
> |
15 |
> tinderbox ~ # equery g lfhex | grep qt |
16 |
> [ 1] x11-libs/qt-gui-4.7.3-r1 |
17 |
|
18 |
i cant speak to this exact case, but the qt libs are a bit special. upstream, |
19 |
it's really one package, but in Gentoo we've split them up into sep ones to |
20 |
make fixing/upgrading in the sub-libs easier/faster. so by depending on any |
21 |
of the qt sublibs, they're hard bound to the qt-core as well. |
22 |
|
23 |
also, your readelf doesnt exactly say that ifhex is using the qt-core API |
24 |
directly. it could only be using qt-gui, but end up pulling in the others |
25 |
implicitly via the qt-gui APIs. so in this specific case, qt-gui requirement |
26 |
only is OK. |
27 |
-mike |