It has been a long time since I packaged for Fedora - but back then, libraries were suppose to be in their own sub-package so that multilib was possible.
But the .mo files that go in /usr/share/locale - if they are in the lib package, would that cause a conflict between both 32-bit and 64-bit versions of the package? I doubt they would be different but the timestamp probably would be.
I tried looking at libgpg-error as that's an example where the .mo files probably should be with the library because a lot of other libraraies use libgpg-error and it can even be installed on systems where people don't use GnuPG because things like xslt can be built against libgcrypt which will pull in libgpg-error.
But Fedora 18 seems to include /usr/bin binaries in with the libpgp-error package making it not multilib capable, so I'm not sure what's going on, is Fedora abandoning multilib philosophy?
But anyway, for a library that is packaged for multilib ([,/usr]/bin stuff in separate package) should the /mo locale files be packaged with the library or in a separate noarch package the library requires? Anyone know what the "best practice" policy Fedora has on this?
But the .mo files that go in /usr/share/locale - if they are in the lib package, would that cause a conflict between both 32-bit and 64-bit versions of the package? I doubt they would be different but the timestamp probably would be.
I tried looking at libgpg-error as that's an example where the .mo files probably should be with the library because a lot of other libraraies use libgpg-error and it can even be installed on systems where people don't use GnuPG because things like xslt can be built against libgcrypt which will pull in libgpg-error.
But Fedora 18 seems to include /usr/bin binaries in with the libpgp-error package making it not multilib capable, so I'm not sure what's going on, is Fedora abandoning multilib philosophy?
But anyway, for a library that is packaged for multilib ([,/usr]/bin stuff in separate package) should the /mo locale files be packaged with the library or in a separate noarch package the library requires? Anyone know what the "best practice" policy Fedora has on this?