On lördagen den 11 april 2009, Barry deFreese wrote: > Now that Gtk1.2 is removed we are also looking to remove glib1.2 from > the archive. It appears that liboop builds fine with libglib2.0-dev as > if it fails to find 1.2 it uses PKG_CHECK_MODULES glib2. Though it is a > bit odd that it doesn't show up as a depends on the lib itself. > (Which is true for the current version as well).
The previous maintainer explains his decision in README.Debian (if you're referring to what I think you are): > 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 anyone > would rather that these were all in separate packages, please let me know > and I'll think again about doing this ... At the moment, the package _DOES > NOT 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 on > the appropriate library (ie. if you link with liboop-tcl, you must also > depend on tcl8.3 ...). The same goes for Build-Depends. > > My reasoning for packaging liboop in this way is to avoid having to install > excessive numbers of large-ish packages (tcl for instance) just to install > your program that depends on liboop. I decided not to change this for the time being, mainly because no packages use the adapter libraries anyway, AFAICT. -- Magnus Holmgren [email protected] Debian Developer
signature.asc
Description: This is a digitally signed message part.
