https://bugzilla.redhat.com/show_bug.cgi?id=1115659 --- Comment #4 from Ralph Bean <rbean@xxxxxxxxxx> --- Yeah, the dependencies to *build* bootstrap were enormous. I wrote a script (npm2spec[1]) to automate it, but getting through the hundreds of reviews took years. If I included buildtime dependencies to run the tests, there were over 1000 upstream projects that needed to be packaged. Even after I got some of these were approved, maintaining the nest of pinned-version deps between all the nodejs components turned out to be overwhelming. I ended up building my own version of bootstrap and hosting a shared copy on fedoraproject.org (a kind of "local to fedora" CDN) or bundling it with the projects that needed it (this ended up being more common). For resultsdb_frontend, I would recommend pointing to a copy of bootstrap using a URL that administrators can configure. By default, it can point to a CDN, but you can optionally host a local-to-your-site copy of bootstrap and configure resultsdb to request it from there. [1] - https://github.com/ralphbean/npm2spec -- 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
