Re: Kurt Roeckx 2007-01-05 <[🔎] 20070105174449.GA13743@roeckx.be>
> > | Depends: [...], libmysqlclient15off (>= 5.0.24-2), libpq4 (>= 8.1.4), libsqlite3-0 (>= 3.3.8)
>
> >From the subject, I seem to understand that those are added by shlibs?
> This seems to suggest that something in the package is linked to all the
> libraries, and I don't see how you could remove it.
The indiviual libyada backends/plugins depend on the corresponding
lib:
[0] cb@sid-amd64.volta:/usr/lib 1j $ldd *yada*.so.4.1.0
libyada.so.4.1.0:
libltdl.so.3 => /usr/lib/libltdl.so.3 (0x0000002a95663000)
libc.so.6 => /lib/libc.so.6 (0x0000002a9576b000)
libdl.so.2 => /lib/libdl.so.2 (0x0000002a959a7000)
/lib64/ld-linux-x86-64.so.2 (0x000000552aaaa000)
libyada_mysql.so.4.1.0:
libmysqlclient.so.15 => /usr/lib/libmysqlclient.so.15 (0x0000002a9565e000)
[...]
libyada_pgsql.so.4.1.0:
libpq.so.4 => /usr/lib/libpq.so.4 (0x0000002a9565e000)
[...]
libyada_sqlite3.so.4.1.0:
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x0000002a9565d000)
[...]
With my suggested change, you could like against libyada itself just fine.
Only when using a specific backend the lib would need to be there.
Of course I'd make sure that the right dependencies were used in the
resulting binaries, just ORed instead of ANDed. It should be possible
to do that in a robust way that doesn't easily break when one of the
databases bumps sonames.
Christoph
--
cb@df7cb.de | http://www.df7cb.de/
Attachment:
signature.asc
Description: Digital signature