https://bugzilla.redhat.com/show_bug.cgi?id=1659556 --- Comment #4 from Martin Pitt <mpitt@xxxxxxxxxx> --- Right, the upstream releases contain pre-built webpacks in dist/. There really is no realistic way to build them as part of a Fedora package build, as it requires internet access (npm install), or shipping hundreds of megabytes of npm modules which are required for building (webpack, babel, eslint, less compiler, etc.). This would only aggravate the problem -- these npm modules themselves are prebuilt (and thus would recursively require an even larger amount of sources, eventually you reach the entirety of the JavaScript world's source), copyright review for these would not be humanly possible (while it's autogenerated for the sources that *do* get shipped). I'm fully aware that this isn't how less insane projects (like C, Python, etc.) get delivered in distributions, but with JavaScript applications there's no other way unfortunately. cockpit, cockpit-ostree, XStatic-Patternfly, etc. do the same thing. We'll get the Source0 fixed, thanks for pointing out! -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
