Follow-up Comment #5, bug #42615 (project gettext):
While I certainly understand the desire and motivation to keep the specific
ITS support with the primary software implementation, because any modification
can then be kept easily in sync. This also causes problems with project
build-depdenencies.
For example I was requested recently to include a policykit policy in dpkg,
and I wanted that to be translated. I had already implemented the .its and
.loc files, to then notice that policykit shipped an .its file, which I was
not able to build-depend on, as that would be unacceptable in this case
because that means pulling policykit into the Debian (or any derivative)
build-essential set.
This can also incur huge build-dependency chains or even cycles, to be able to
support files that are not directly used by the building projects. So shipping
all these files with gettext also have some merit worth considering IMO.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42615>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
