I'm reviewing rakudo <https://bugzilla.redhat.com/show_bug.cgi?id=498390>, a Perl 6 interpreter. The interpreter is mostly written in NQP language and the sources are compiled into MoarVM object files at RPM package build time. The moarvm files are installed under /usr/share subdirectories. The problem is the moarvm files differ in size (and thus in content) among architectures. My first impression was that the files must be moved under %{__libdir}. But I'm not fully convinvced it is really necessary. First, the moarvm files should be portable despite of different size. At least this my unverified opinion. If it were true, could we put the files into a noarch subpackage? Wouldn't that break Fedora release managament? Second, if rakudo did not aspire for multilib safety (rakudo contains some ELF files), would it be permissible to keep the moarvm files under /usr/share and delivered by architecture-specific RPM package? Maybe my questions could be summarized as: How should the FHS definition ("The /usr/share hierarchy is for all read-only architecture independent data files") should be understood? The files must be bit-to-bit indistinguishable, or the files can be used on any architecture? -- Petr
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
