Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=575005
--- Comment #39 from Peng Huang phuang@redhat.com 2010-04-22 00:46:44 EDT --- (In reply to comment #37)
(In reply to comment #35)
Reading though this it will be simpler for long term management for this to be architecture specific. rpm doesn't understand endianness and trying to shoehorn it in makes it much more complicated and difficult to work with.
Where should we install those endian-specfic files %{_prefix}/lib, %{_datadir} or %{_libdir}? The default install path for those files are normally %{_datadir} and many softwares which utilize endian-specfic data hardcode /usr/share/%{name} in its code. It'll be a bit complicated to patch some package to install or utilize those files from %{_datadir} to %{_libdir}.
I think it is acceptable to install arch specified *DATA* files in %{_datadir} too. Probably we can not find out a 100% perfect solution right now, but I think we could improve it in future. I still suggest resolving this problem in upstream. Let zinnia use non endian-specific data file.
BTW, I think our major platfroms (i386 and x86_64) using the same endian.
i18n-bugs@lists.fedoraproject.org