Differences between revisions 6 and 8 (spanning 2 versions)
Revision 6 as of 2014-05-10 12:57:38
Size: 3657
Editor: LeoIannacone
Comment: updated.
Revision 8 as of 2014-05-10 13:25:10
Size: 3605
Editor: LeoIannacone
Comment: relax node packages name - "should" be called node-foo
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
 0. the ''binary'' package name '''must''' be called '''node-foo''' and the ''source'' package name '''should''' be called the same  0. the ''binary'' the source package name '''should''' be called '''node-foo'''
Line 22: Line 22:
 0. '''should''' generate a '''libjs-foo''' binary package if the script is usable also for web-broser (see [[Javascript/Policy]]) for more info)  0. '''should''' generate a '''libjs-foo''' binary package if the script is usable also for web-broser (see [[Javascript/Policy]] for more info)

This document is still work in progress.

Please check the mailing list archives for the latest discussions about it.

Node.js modules policy

This page describes the policy that packages with Node.js modules should follow.

Policy in brief

  1. the binary the source package name should be called node-foo

  2. must build depends on nodejs

  3. should be installed to /usr/lib/nodejs/ or /usr/lib/nodejs/foo/, depends whether the module is contained in a single file or in multiple files

  4. should have package.json shipped in /usr/lib/nodejs/foo/package.json

  5. should generate a libjs-foo binary package if the script is usable also for web-broser (see Javascript/Policy for more info)

Policy in details

Install

A module typically has already a source tree layout with directories like "lib", "bin", and a package.json file at its root.

Installing is as simple as:

  • debian/install
    lib          usr/lib/nodejs/<module>
    bin          usr/lib/nodejs/<module>
    package.json usr/lib/nodejs/<module>
  • debian/links
    usr/lib/nodejs/<module>/bin/<mybin>.js   usr/bin/<mybinOrRenameProperly>
  • debian/dirs
    usr/bin

This usually allows source to be kept unpatched (except for the nodejs rename):

  • relative require statements like  require('..')  work

  • lookups in package.json like  require('./package').version 

  • load module from NODE_PATH :  require('mymodule');  still work

Please refer to the upstream documentation (also available in /usr/share/doc/nodejs/api/modules.html#modules_folders_as_modules) to understand how to correctly Node.js looks up for modules.

Excluding auto-generated files from source

Strict application of DFSG requires files generated from source in upstream tarball to be excluded, unless it is possible to regenerate the files and prove they are identical to the ones in the tarball.

Minified files and browserified files are examples of such files that could be excluded for that reason. A convenient way to achieve this is to use the Files-Excluded field in debian/copyright, for more information please see UscanEnhancements.

Declare a build-dependency on nodejs

The nodejs package depends on libv8 and doesn't build on some architectures. Because of that, node-* packages having "Architecture: all" are available on architectures where nodejs isn't available - and so are uninstallable on those architectures. To work around that inconvenience to the users, simply declare an unversioned "Build-Depends: nodejs".

Declaring that build-dependency is also quite natural in the case of a package running its test suite during its build.

Patching binaries shebang

While the entire world use node as command name for Node.js framework, in Debian the correct name is nodejs, because it conflicts with another package called node as well.

Technical committee decided to fix this by renaming node to nodejs.

To comply to this, it is often as simple as:

  • change shebangs to #!/usr/bin/nodejs
  • rename node to nodejs in makefiles
  • do not depend on nodejs-legacy

Some programs are a bit less obvious to fix, for example they can spawn nodejs instances using "node" name.