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 Liang Suilong <liangsuilong@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |liangsuilong@xxxxxxxxx --- Comment #42 from Liang Suilong <liangsuilong@xxxxxxxxx> 2010-04-22 10:01:51 EDT --- The data is not architecutre dependent. It should be endian dependent. If different architectures blog to the same endian, the package can share with another architectures. An x86_64 users does not want to install a package in order to keep compatibie if it is not recommended, because an extra package means it will take more spaces. I wrote a spec sample for zinnia-tomoe. It will be built independently for little-endian and big-endian. https://dl.dropbox.com/u/1352061/zinnia-tomoe/zinnia-tomoe-sample.spec And I modify the zinnia-tomoe-fixes-makefile.patch. The default installation path will switch to %{_datadir}. Here is koji result: http://koji.fedoraproject.org/koji/taskinfo?taskID=2132276 SPEC: https://dl.dropbox.com/u/1352061/zinnia-tomoe/zinnia-tomoe.spec SRPM: https://dl.dropbox.com/u/1352061/zinnia-tomoe/zinnia-tomoe-0.6.0.20080911-4.fc12.src.rpm As we know, maintaining source codes is much more difficult to maintain spec files, especially for me, not an professional coder. For many packagers, they have no enough skill to modify the codes. So we can see the best way to modify the spec file under packaging guideline. If we put endian-dependent data to %{_libdir}, it will mean that quite many package should be requested to change their codes. Comparing to codes, it is an easy job to edit spec files. At last, in my opinion, Fedora should have a new guideline to teach packagers how to build a endian-dependent package. -- 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