On Tue, Jul 20, 2021 at 7:24 AM Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > > On Tue, Jul 20, 2021 at 06:29 Vitaly Zaitsev via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: >> >> On 20/07/2021 11:18, Nico Kadel-Garcia wrote: >> > You're violating the bundling and naming practices that EPEL and >> > Fedora have used for years, especially their insistence that they >> > build from source, not repackaging bundled binaries from someone else >> > into an RPM. >> >> This is not a Fedora package. This is a COPR package. > > Your wording in your initial emails made it sound like this was a package either in EPEL or going to be in EPEL. In a very rare case, I was in agreement with Nico and going to say the same things they did. Thank you for clarifying this but it was confusing. I didn't see COPR mentioned either. The title referred to EPEL 7. >> COPR guidelines allows usage of pre-built binaries if they don't violate >> the Fedora Legal guidelines[1]: "You do not need to comply with >> Packaging Guidelines". Even if COPR guidelines allow it, Vitaly, it's a bad idea. I'm startled that the jar files can compile in COPR if they don't compile in the normal Fedora environment. I suspect they can't, the .spec file in the git repo you mentioned doesn't pull source. It pulls a pre-compiled tarball from In theory, Java provides "write once, run everywhere". In practice, especially cross-linked with other libraries such as the libffi packages for C data structures.... not so much, as you've just encountered. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
