That sounds like a Change Proposal for F28. So your idea would be to mass-retire all but the most common or security-sensitive NPMs from Fedora and rely on bundling in most cases?
That will also mean coming up with a strategy for removing those unbundled packages on updates. Thoughts on that? On Wed, Sep 20, 2017, 4:59 AM Zuzana Svetlikova <[email protected]> wrote: > I was wondering, could we use bundling and clean up the mess that is > current nodejs stack in Fedora? > > To be more precise, there are currently over 2000 packages and over 500 > nodejs-* is available bugs, > that nobody has time to fix and/or feels like fixing, because updating one > module might/will break several others. > > For the sake of maintainability, I'd like to leave as little packages as > possible. > > On Thu, Sep 14, 2017 at 6:45 PM, Stephen Gallagher <[email protected]> > wrote: > >> >> >> On Wed, Aug 9, 2017 at 8:06 AM Stephen Gallagher <[email protected]> >> wrote: >> >>> I haven't had any time to work on it, but I'd very much like to develop >>> an automatic RPM dependency generator that will recurse down the >>> node_modules directories, read their package.json files and automatically >>> create those Provides. If anyone else wants to take a crack at doing that, >>> it would be an immense help. >>> >> >> A big thank-you needs to go to Tomas Tomacek for >> https://pagure.io/nodejs-packaging/pull-request/2 which is now in effect >> on Fedora 28 (Rawhide) builds. >> >> So now any Node.js package that is built in Fedora will automatically >> have `Provides: bundled(nodejs-foo)` added automatically. >> >> _______________________________________________ >> nodejs mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> >> _______________________________________________ > nodejs mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ nodejs mailing list -- [email protected] To unsubscribe send an email to [email protected]
