Blame | Last modification | View Log | RSS feed
liboop for Debian-----------------I've chosen at this stage not to package the adapter libraries separately,since the package only weighs in at just over 500k when unpacked. If anyonewould rather that these were all in separate packages, please let me knowand I'll think again about doing this ... At the moment, the package _DOESNOT DEPEND_ on any of the libraries required to use the adapter libraries,so if your package uses one of the adapter libraries, you _must_ depend onthe appropriate library (ie. if you link with liboop-tcl, you must alsodepend on tcl8.3 ...). The same goes for Build-Depends.My reasoning for packaging liboop in this way is to avoid having to installexcessive numbers of large-ish packages (tcl for instance) just to installyour program that depends on liboop.I haven't compiled in the libwww adapter support - this is primarily becausethe current libwww0 package in Debian doesn't include libwwwxml, because whenthis library is compiled there is a name clash (libwww also includeslibxmltok and libxmlparse, which are in the libxmltok1 package). It'sdifficult to compile liboop support for libwww libraries excluding libwwwxml,as the configure script simply links liboop-www with all of the libwwwlibraries, including libwwwxml. I'm working on a solution to this with thelibwww maintainer. In the meantime, liboop Build-Conflicts: libwww-dev. Ifyou need this support urgently, feel free to contact me and I'll hurry upmy work on this (no real urgency at the moment, however ...)-- Timshel Knoll <timshel@debian.org> Tue, 5 Mar 2002 15:41:41 +1100