Re: nodejs packaging in Fedora

2017-09-20 Thread Tom Hughes
Binary compiled ones probably also need to be kept. Presumably this also means identifying "top level" packages that are an end goal in themselves and need to be kept. Tom On 20/09/17 11:11, Stephen Gallagher wrote: That sounds like a Change Proposal for F28. So your idea would be to

Re: nodejs packaging in Fedora

2017-09-20 Thread Zuzana Svetlikova
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

Re: nodejs packaging in Fedora

2017-09-14 Thread Stephen Gallagher
On Wed, Aug 9, 2017 at 8:06 AM Stephen Gallagher 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

Re: nodejs packaging in Fedora

2017-08-20 Thread Stuart Gathman
On 08/09/2017 08:06 AM, Stephen Gallagher wrote: > > > On Fri, Aug 4, 2017 at 10:43 AM Troy Dawson > wrote: > > Although this looks tempting, it's only looking at half the problem. > Versions > Nodejs modules get updated all the time, at

Re: nodejs packaging in Fedora

2017-08-09 Thread Stephen Gallagher
On Fri, Aug 4, 2017 at 10:43 AM Troy Dawson wrote: > On Fri, Aug 4, 2017 at 6:48 AM, Stuart D Gathman > wrote: > > I've started working on packaging scuttlebot for Fedora. I see that we > now have a Fedora package for every nodejs module. This makes it

nodejs packaging in Fedora

2017-08-04 Thread Stuart D Gathman
I've started working on packaging scuttlebot for Fedora. I see that we now have a Fedora package for every nodejs module. This makes it easy to map directories in node_modules to package names - however, it means submitting hundreds of packages to ever get scuttlebot submitted. I'm