On Mon, Oct 4, 2021, at 3:08 PM, Fabio Valentini wrote: > But then you're back to *exactly how Fedora packages for Java projects > already work* - only with the added complication that distributing > those build artifacts as plain JARs instead of RPMs now makes them > impossible to consume as dependencies from other RPM builds. One needs to be a bit careful using the term "impossible" in software. Some things, such as the halting problem have actually been proven impossible. But this is not impossible =) I use non-RPM things as part of building RPMs all the time. So do many other systems. I think you instead mean e.g.: "would require our use of RPM to not be fully self-hosting" or "would require some tooling to e.g. automatically generate RPMs from external binaries" etc. That's more of a policy question, far from impossible. _______________________________________________ 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
