> Am 01.06.2021 um 11:47 schrieb Mat Booth <fedora@xxxxxxxxxxxxxx>: > > > Note that while Wildfly *was* packaging in Fedora, it no longer is > because it amounted to more than one person's full time job to keep it > and its dependencies updated and working in Fedora. Thanks, so my reconstruction is basically correct (minus my impression it never got to fly). > For some history, > please see Marek's email from 2015: > https://lists.fedoraproject.org/archives/list/java-devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/SD26DWKQRKF4PIW656NKSRZXBJUP2PI4/ Max Rydahl Andersen made some interesting remarks at the end, e.g. "drop the need for individual synced rpm's of each jar,“ Was there an attempt to do this? And would that really reduce the load so much that an rpm would be possible? Sorry, may be a dumb question. I’m just trying to (re)sort the options. The copr rpm at https://copr.fedorainfracloud.org/coprs/g/wildfly/wildfly/ will certainly never make it into an official Fedora release or other distributable because of the automatic download of an external binary. Our idea is to make the system admin download the binary and when he decides to to that, assist him ("officially") to install it properly (and easily). It it works, I don’t know. Di you see alternative options? _______________________________________________ java-devel mailing list -- java-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to java-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/java-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
