On Fri, 25 Nov 2011, Steve Langasek wrote: > No, having to split this data out into separate packages is a significant > cost for maintainers and on the archive and simply the wrong way to do it. > Automatic package splits for the likes of tdebs are fine, but we should not > be forced to split binary packages in the archive for data files such as .mo > files that could readily be made architecture-independent.
Ok, I'm not 100% convinced, but after reading this, I'm willing to ask gettext authors that they make little-endian the default again, or at least they tell me how we could achieve that (configure options, environment variables, whatever). Steve: Could you please report this as a *new* bug and summarize the problems that native endianness in gettext create to multi-arch? (I would prefer to keep this issue as a different one from the old bug). A Subject like "msgfmt creates mo files in native endianness" would be fine. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
