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 #46 from Chen Lei <supercyper1@xxxxxxxxx> 2010-05-06 23:15:12 EDT --- (In reply to comment #45) > Here are summary of this bug's current status here: > This bug is discussing about how to deal with the binary model file, and about > 3 solutions are posted here: > 1. Consider zinnia-tomoe model data file arch-dependent, put the binary model > in %{_libdir}, or %{_datadir} with the the arch name as the model file postfix. > 2. Consider zinnia-tomoe model data file endian-dependent only, and provide > both big-endian and little-endian model file. > 3. Make a patch for zinnia, and make the model file completely > arch-independent. (Thanks for Peng Huang's patch, sent to upstream.) > Personally I prefer the solution 1 from Dennis Gilmore, and copy his comment > here: > >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. > Please decide how to solve this problem, thanks in advance. I'd like to simply install small endian-specfic data into %{_datadir}, but without noarch for those package. For big endian-specific data, I suggest to split them into two noarch subpackages. Tweak spec is much more eaiser than patching software to use arch-independent endian files or utilize endian-specfic data in %{_libdir}. History show many packages install their endian-specfic data into %{_datadir}, but few packages install those data into %{_libdir} as I known. e.g. gcin: Input method for Traditional Chinese scim-fcitx: FCITX Input Method Engine for SCIM espeak: Software speech synthesizer (text-to-speech) Notes: Their are also some disscussion on debian's mail list. For espeak, the final decision is simply revoking noarch for espeak-data. See http://packages.debian.org/sid/espeak-data For sunpinyin(big data), the final decision is split endian-specfic data into two noarch subpackages. If we decide to treak endian-specfic as arch-specfic, then a lot of packages in repo need patching. Also, it may waste space for end users, if we considring multilib circumstance. For F13, all primary arch is little endian now, splitting big endian-specfic data into noarch subpackage will also save space in fedora mirrors. -- 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