| 1 |
On Friday 28 March 2003 23:55, Robin H. Johnson wrote: |
| 2 |
> On Fri, Mar 28, 2003 at 05:54:54PM +0100, Per Wigren wrote: |
| 3 |
> > But how do we check that with the current information? |
| 4 |
> > To use the postfix-case above as an example.. |
| 5 |
> > Postfix works fine with both MySQL v3.x and MySQL v4.x. |
| 6 |
> > If it is compiled against v3 it has to be recompiled if MySQL is upgraded |
| 7 |
> > from v3 to v4, but not if it is upgraded from v4.0.11 to v4.0.12.. |
| 8 |
> > |
| 9 |
> > To use MPlayer as another example.. |
| 10 |
> > MPlayer has to be recompiled EVERY TIME that DirectFB is upgraded, even |
| 11 |
> > minor version, because it links to .so.<complete versionnumber> .. But |
| 12 |
> > it doesn't need to be recompiled if for example Vorbis is upgraded from |
| 13 |
> > v1.0.1 to v1.0.2 or even v1.8.5 because it links to libvorbis.so.0 ... |
| 14 |
> |
| 15 |
> The MPlayer and MySQL examples are different. For MPlayer it's the link |
| 16 |
> to .so.<complete versionnumber> that means you need to recompile. |
| 17 |
> |
| 18 |
> But for MySQL v4, even if you linked just to the plain .so, you had to |
| 19 |
> recompile, because the API and structures changed. If you just left it |
| 20 |
> there and tried to run things, they would segfault. |
| 21 |
|
| 22 |
Yes, "of course".. It links to the major versionnumber for a reason... |
| 23 |
The MySQL-libraries are ABI-compatible withing the major version so it doesn't |
| 24 |
need to link to .so.x.y.z or .so.x.y, just .so.x. |
| 25 |
DirectFB is still under development (beta/alpha) and is not ABI-stable, so |
| 26 |
programs are linking to .so.x.y.z.. |
| 27 |
IMHO the only good way to track what packages should be recompiled is to check |
| 28 |
what it links to with ldd. If a program links to the .so instead of .so.x.y |
| 29 |
of a library that is not considered ABI-stable, it should be seen as a bug in |
| 30 |
the program. |
| 31 |
|
| 32 |
// Per Wigren |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives