Hi,
On Tue, 23 Sep 2014 12:15:22 -0400
Darin Perusich
However, to deal with the large number of packages I had to submit, I wrote a script to fetch module information from registry.npmjs.org, download the tarball, and generate the spec file. It's a bit basic at the moment (e.g. it doesn't take version numbers of dependencies into account), but I guess it could be extended to handle that and also to handle updates rather than new packages only. Due npm registry and the (mostly) uniformity of node modules, those tasks are fairly well scriptable which could take some of the pain away. I'll look into it.
Is this script you mention available? I've been holding off on packaging a few nodejs packages, puppet-explorer specifically, due to not wanting to get into the dependency nodejs hell that npm was about to unleash.
I haven't looked into writing a more general-purpose node.js packaging script yet. So far I only have that script to create new node packages. If that's of any use for you, I can send it to you. Regards Joe -- ISV Technical Manager SUSE LINUX Products GmbH -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org