![]() ![]() Because of that, node-* packages having " Architecture: all" are available on architectures where nodejs isn't available - and so are uninstallable on those architectures. The nodejs package depends on libv8 and doesn't build on some architectures. A convenient way to achieve this is to use the Files-Excluded field in debian/copyright, for more information please see Javascript/Repacking and UscanEnhancements. Minified files and browserified files are examples of such files that could be excluded for that reason. 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. ![]() 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.Įxcluding auto-generated files from source Load module from NODE_PATH : require('mymodule') still work Lookups in package.json like require('./package').version ![]() Relative require statements like require('.') work This usually allows source to be kept unpatched: debian/links usr/lib/nodejs//bin/.js usr/bin/.Should integrate automatic tests checking require('foo') works correctlyĬompiled c++ addons should Depend on nodejs-abi-Ī module typically has already a source tree layout with directories like "lib", "bin", and a package.json file at its root. Should generate a libjs-foo binary package if the script is usable also for web-browser (see Javascript/Policy for more info) Should have package.json shipped in /usr/lib/nodejs/foo/package.json 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 The binary and the source package should be called node-foo ![]() This page describes the policy that packages with Node.js modules should follow. Please check the mailing list archives for the latest discussions about it. ![]()
0 Comments
Leave a Reply. |