On 2012-08-14 16:08, P. J. McDermott wrote: > 2. Split the remaining libraries out of gettext (my original proposed > solution). Mark gettext Multi-Arch: foreign and the new libraries > package(s) Multi-Arch: same. > 3. Remove the aforementioned symbolic links and declare the libraries > in gettext "for internal use only" (as is libbfd-2.22-system.so in > binutils, for example).
Sorry, these aren't exactly complete, as Steve notes: On 2012-08-14 16:00, Steve Langasek wrote: > libgettext-dev is the main piece that is still missing to make all relevant > bits of gettext co-installable: currently the .so symlinks for the public > runtime libraries, which are needed at build time by packages linking > against the libs, are shipped in the 'gettext' binary package; so when > cross-building a package that build-depends on gettext, we have to know > whether they're using the tools or the libraries. So if nothing else, libgettext-dev should be split out from gettext. The remaining question is whether the libraries that are still in gettext are to be used by other packages. -- P. J. McDermott (_/@\_) ,--. http://www.pehjota.net/ o < o o > / oo \ http://www.pehjota.net/contact.html o \ `-/ | <> |. o o o "~v /_\--/_/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
