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

Re: Including separately distributed translations in deb

Hash: SHA1

Ricardo Mones schrieb:
> On Wed, 26 Oct 2005 15:18:42 +0200
> Torsten Marek <shlomme@gmx.net> wrote:
>>I'm the maintainer of eric (eric.sourceforge.net). Upstream
>>distributes the translations of eric (de, ru, fr) separately from
>>eric, and up to now I've included the compiled message catalogs (qm,
>>eric is a PyQt program) into a regenerated orig.tar.gz. Since they
>>are binary files, it's not possible to include them into the Debian
>>diff. However, I could include the textual translation files (the
>>po's, so to say) into the diff.gz and compile them when the package
>>is built. Which solution is better? In the first, the orig.tar.gz is
>>not "original", in the second the diff.gz get quite big (the
>>uncompressed message catalogs are ~700kiB each).
>   Assuming those binary translations are arch-independent (which is the
> usual case) I'd suggest to make a new package for them with arch
> 'all' (for example 'eric-i18n'). Is a waste of space and time to
> rebuild them every time for all architectures. If upstream provides
> them built is even better (package will be built faster ;) 
>   regards,

eric itself is arch: all, the this would not be a problem. Still, if I created
an eric-i18n package, I would have to merge all the separate translation
tarballs (one per language) into one package. Is there a best-practice for this?



- --
Torsten Marek <shlomme@gmx.net>
ID: A244C858 -- FP: 1902 0002 5DFC 856B F146  894C 7CC5 451E A244 C858
Keyserver: subkeys.pgp.net

Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


Reply to: