"This macro should be called in the %install section of every Node.js module package."
- Actually, I'd rather it be called even for modules without deps, since it'll just do nothing. That way there won't be problems if the module adds deps later. I just added some language to this effect. --Patches (talk) 06:34, 17 January 2013 (UTC)
- Do these implementations implement the node standard library (e.g.
require())? Do they read package.json to identify the entry point for the module? Do they offer any compatibility with the Node.js native module ABI? Most of the packages I've done so far have explicit dependencies on the node engine in their package.json.
sitelib and sitearch
Is there notion about vendorlib and vendor arch as well? There are all four directories available in Ruby and there is small distinction in their meaning. The vendorlib is used for stuff distributed by vendor while sitelib is for libraries installed by local admin, therefore in Ruby, the vendorlib points to /usr/shared where sitelib points to /usr/local. - Vít Ondruch 2013-01-17 12:47 UTC
- Nope. The only search path node uses is ./node_modules. /usr/lib/node_modules is an npm convention, and installing RPMs there allows users to use
npm linkto bring them into their personal projects. For more information on how module loading in node works, see this message on fedora-devel --Patches (talk) 02:02, 18 January 2013 (UTC)
Second question for the same topic, which is sitelib poiting into /usr/lib? Shouldn't the files go into /usr/share, since they are platform independent? - Vít Ondruch 2013-01-17 12:47 UTC