"Torsten Marek" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Hi,
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?
IANADD, but it seems to be fine to merge the translation tarballs. However
perhaps to make things
easier, as the end package would have only limited resemblence to any
upstream package, is to package the translations as a 'native' package. That
is perfectly valid. It is a question a what saves you the most work.
greetings
Torsten
- --
Torsten Marek <[EMAIL PROTECTED]>
ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858
Keyserver: subkeys.pgp.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDX5FqfMVFHqJEyFgRAuP6AJ9GbXdHKb7J8PGK1don4jZQ+93AIwCdH8jM
j38Pt77Vk2K7Io7RhVEio78=
=zq+0
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
