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 #21 from Chen Lei <supercyper@xxxxxxx> 2010-03-27 01:30:29 EDT --- Some more packages that put endian-specific data into %{_datadir}: http://koji.fedoraproject.org/koji/fileinfo?rpmID=1731290&filename=/usr/share/espeak-data/mk_dict http://koji.fedoraproject.org/koji/fileinfo?rpmID=1731299&filename=/usr/share/espeak-data/mk_dict http://koji.fedoraproject.org/koji/fileinfo?rpmID=1731296&filename=/usr/share/espeak-data/mk_dict http://koji.fedoraproject.org/koji/fileinfo?rpmID=1731293&filename=/usr/share/espeak-data/mk_dict I really want to put arch-specific files into directories other than %{_datadir}, however I think we should treat endian-specific files seriously and follow packaging convention. We cannot simply consider endian-specific data as arch-specific, because little-endian data and big-endian data are just the counterpart of the other through byte swapping. I'll try to find more examples on how to treat endian-specific files, or is it right to ask FPC's opinion on how to treat those data? If we decide to put all endian-specific data into {_libdir} or /usr/lib, maybe we need to patch a large amount of packages that already existed in the repo of fedora. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review