[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug-gettext] Reproducible builds and .mo file endianness

From: Santiago Vila
Subject: [bug-gettext] Reproducible builds and .mo file endianness
Date: Tue, 5 Jan 2016 01:43:36 +0100 (CET)
User-agent: Alpine 2.11 (DEB 23 2013-08-11)

Hello again.

I believe you might have heard about the "reproducible builds" effort:


There is a thing which we have not tested yet but I hope that will be
tested some day: Architecture-independent packages created from a
given source package should ideally not depend on the host
architecture the package is being built.

(This would include packages containing just .mo files).

Before this, Debian had a reason to modify msgfmt so that it always
outputs little endian .mo files. It was called "multiarch": Packages
from different architectures which are to be installed simultaneously
on the same system should have their overlapping files byte-by-byte

But now we have two reasons for this: multiarch and reproducible builds.

So I think this is the right time to ask:

Would you please reconsider about msgfmt default behaviour?

This is the patch that the Debian gettext package has for this issue
since version (dated May 2012).

Is there a possibility that we don't need this patch anymore some day?

If adopting the patch "as is" is not possible, a new ./configure option
for this would be a lot better than nothing, see the previous email
where I explain the undesired msgfmt.1 regeneration that happens
during the build.


Attachment: 02-msgfmt-default-little-endian.diff.txt
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]