From Fedora Project Wiki

Revision as of 12:48, 17 January 2013 by Vondruch (talk | contribs)


"This macro should be called in the %install section of every Node.js module package."

Shouldn't that be "This macro should be called in the %install section of every Node.js module package that depends on other modules."? Churchyard (talk) 02:10, 17 January 2013 (UTC)

  • 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)

Naming conventions

I am not sure about the nodejs- prefix. At the end, the package contains just JavaScript files, which might be executed by whatever JS engine available on the system, which is by coincidence Node.js ATM, but it could be other interpreter in the future. For example, there exist rubygem-execjs library, which can execute JavaScript files using vairous JavaScript engines, starting by Node, SpiderMonkey, V8 and ending by Microsoft Windows Script Host (although this one is not relevant on linux ;) Yes, I understand that there might be some shebang, that points to node, but we are now solving similar issues in Ruby world, due to JRuby - Vít Ondruch 2013-01-17 12:26 UTC

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

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