Hi -mentors ...,
I'm currently in the process of packaging liboop (www.liboop.org), which
is an event loop management library that comes with "adapters" for
various other libraries (currently tcl, libadns, libwww, libglib and
libreadline). These adapter libraries are installed as
/usr/lib/liboop-{adapter-name}.so.x.x.x and are linked with the
appropriate library.
1) Package all packages and the main library in a "liboop3" package
which depends on installing all of the dependancies. This is probably
the worst solution, as any library that links with liboop will also
depend on tcl, libadns, libwww ... :-(
2) Package all packages and the main library in a "liboop3" package, but
_don't depend_ on any of the adapter library's linked libraries. This
will work dependancy-wise, since any library that links with
liboop-tcl will also link with libtcl8.3, so the appropriate
dependancies will be installed. I could also change the shlibs for
the library to read:
"liboop-tcl 0 liboop (>= vers), libtcl8.3"
just to be sure ... This method leaves unresolved symbols in each of
liboop's adapter libraries until the appropriate library is
installed ... does this fit in to policy?
3) Package the main library in a "liboop3" package, but package adapters
in "liboop-{adapter}{soname}", ie. liboop-adns0 which depends on
liboop and the appropriate library that it is linked against. This I
suppose is the "ideal" solution, but adds to an ever-increasing
package bloat in the dist. Most of the adapter libraries are quite
small (<= 5k uncompressed), so I believe that this is overkill.
ATM, I'm leaning for option 2), but am unsure of the policy on this.
Anyone with feedback?
Cheers,
Timshel
--
Timshel Knoll <[EMAIL PROTECTED]> for Debian email: <[EMAIL PROTECTED]>
Debian GNU/Linux developer, see http://people.debian.org/~timshel/
For GnuPG public key: finger [EMAIL PROTECTED]
msg05609/pgp00000.pgp
Description: PGP signature
