Hi, On Mon, Aug 13, 2012 at 01:30:12PM +0200, Santiago Vila wrote: > On Thu, 9 Aug 2012, P. J. McDermott wrote: > > I wonder if the gettext binary package should instead be split. > > Perhaps gettext-runtime (M-A: same) should provide the libraries, > > gettext-tools (M-A: foreign) should provide the tools, and gettext > > should be a metapackage that depends on both of the former packages? > > So: What exactly did you mean by "split"?
Steve made the gettext binary package M-A: allowed so that packages depending on it can choose (using the :any qualifier in their dependencies) whether they need a native version of the gettext binary package or if a foreign version will do as well. Patrick's idea was to split the gettext binary package into two packages: one package that would contain those parts that satisfy dependencies of packages of every other architecture (this package would be M-A: foreign) and one package that would only allow to satisfy dependencies of packages of the same architecture (this package would be M-A: same). Looking at the content of the gettext binary package, the following files would surely go into the M-A: same package as they differ between architectures: /usr/lib/gettext/hostname /usr/lib/gettext/urlget /usr/lib/libasprintf.a /usr/lib/libgettextlib-0.18.1.so /usr/lib/libgettextlib.so /usr/lib/libgettextpo.a /usr/lib/libgettextsrc-0.18.1.so /usr/lib/libgettextsrc.so /usr/lib/preloadable_libintl.so /usr/share/java/gettext.jar The following binaries also differ across architectures but those executables might be able to fulfill dependencies on them even for foreign architectures? /usr/bin/gettextize /usr/bin/msgattrib /usr/bin/msgcat /usr/bin/msgcmp /usr/bin/msgcomm /usr/bin/msgconv /usr/bin/msgen /usr/bin/msgexec /usr/bin/msgfilter /usr/bin/msgfmt /usr/bin/msggrep /usr/bin/msginit /usr/bin/msgmerge /usr/bin/msgunfmt /usr/bin/msguniq /usr/bin/recode-sr-latin /usr/bin/xgettext I'm not familiar with gettext so I couldnt tell which of above binaries would satisfy foreign dependencies on them and which do not. IMHO, if possible, then compared with making the gettext binary package M-A: foreign, splitting the gettext binary package into a M-A: foreign and a M-A: same package would be the preferred option. One reason for that is, that the :any qualifier is not yet allowed to be used in Debian because wanna-build doesnt understand it yet. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
