The most basic way of using browserify is not really consistent with the Debian approach. In most packages, we do everything to avoid having bundled libraries (e.g. in a C++ project) and aim to have each library in its own package so that any one library can be updated individually to fix a bug or security flaw.
If I use browserify(-lite) from debian/rules, then it is copying code from other packages into my own binary package at build time. Instead of running browserify from debian/rules, maybe browserify can be run dynamically by some hook script each time dependency packages are installed or upgraded? This would mean the browserify output is not kept in any real binary packages, it is built locally on each system and stored in /var/cache perhaps _______________________________________________ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel