On 2017, ഡിസംബർ 18 11:44:57 PM IST, Hilko Bengen <ben...@debian.org> wrote:
>I am working on packaging a new version of GRR, an incident response
>platform that is written mostly in Python, with a browser-based UI
>built/combined using Gulp using several plug-ins that are not in
>requiring a flood of other NodeJS packages, all in all more than 20 of
>them. Below is my initial list of packages that are not in
>Q1: Am I really supposed to prepare, upload, and eventually maintain
>those packages so I am able to build that browser UI component? Or is
>there another way?
If you want it in main, then yes. Another possibility is to have it in contrib.
>Q2: I noticed that the node-gulp-less package created by npm2deb
>on node-less (>= 2.6.0), the current version of node-less in unstable
>1.6.3~dfsg-2. The version number difference (assuming semantic
>versioning) suggests API breakage between the versions, so simply
>upgrading node-less is probably not an option. Is it possible to have
>multiple versions of NodeJS packages with the same name installed into
No, this will need a transition, ie, all packages depending in node-less will
need to be updated to work with the new version.
>- gulp-angular-templatecache: event-stream, gulp-header, gulp-footer
>- gulp-footer: event-stream
>- event-stream: from, map-stream, pause-stream, stream-combiner
>- gulp-closure-compiler: temp-write
>- gulp-if: gulp-match ternary-stream
>- gulp-insert: stream-queue
>- gulp-less: accord, less >= 2.6.0
>- accord: indx
>- gulp-sass: node-sass
>- node-sass: async-foreach, gaze, in-publish, sass-graph,
You can use a script to generate the dependency list like
Sent from my Android device with K-9 Mail. Please excuse my brevity.