Re: [Pkg-javascript-devel] where do I begin? I want to package many node module dependencies for an application

2014-06-29 Thread Andrew Kelley
By the way here is npm2deb running on groovebasin. There are many
unfulfilled dependencies:

Dependencies:
NPM   Debian
groovebasin (1.1.0)   None
├─ cookies (~0.4.1)   None
│  └─ keygrip (~1.0.0)None
├─ connect-static (~1.1.1)None
│  ├─ pend (~1.1.1)   None
│  ├─ streamsink (~1.0.1) None
│  ├─ findit (~1.1.1) None
│  └─ mime (~1.2.11)  node-mime (1.2.11-1)
├─ music-library-index (~1.2.0)   None
│  └─ diacritics (^1.1.0) None
├─ zfill (0.0.1)  None
├─ semver (~2.3.1)node-semver (2.1.0-2)
├─ jsondiffpatch (~0.1.7) None
│  └─ chalk (~0.4.0)  None
│ ├─ strip-ansi (~0.1.0)  None
│ │  └─ ansi-regex (^0.2.1)   None
│ ├─ has-color (~0.1.0)   None
│ └─ ansi-styles (~1.0.0) None
├─ ytdl (^0.2.8)  None
│  ├─ progress-bar (~0.1.1)   None
│  ├─ streamify (~0.2.0)  None
│  │  ├─ readable-stream (~1.1.9) None
│  │  │  ├─ isarray (0.0.1)   None
│  │  │  ├─ string_decoder (~0.10.x)  None
│  │  │  ├─ inherits (~2.0.1) node-inherits (2.0.0-1)
│  │  │  └─ core-util-is (~1.0.0) None
│  │  └─ hashish (~0.0.4) None
│  │ └─ traverse (=0.2.4)node-traverse (0.6.1-1)
│  ├─ request (~2.34.0)   node-request (2.26.1-1)
│  ├─ jstream (~0.2.7)None
│  │  ├─ clarinet (~0.8.1)None
│  │  └─ readable-stream (~1.1.9) None
│  ├─ nomnom (~1.6.1) None
│  │  ├─ colors (0.5.x)   colors.js (0.6.2-1)
│  │  └─ underscore (~1.4.4)  underscore
(1.4.4-2ubuntu1)
│  ├─ eventvat (~0.2.1)   None
│  │  └─ eventemitter2 (=0.4.x)  None
│  ├─ colors (~0.6.0-1)   colors.js (0.6.2-1)
│  ├─ underscore (~1.6.0) underscore
(1.4.4-2ubuntu1)
│  └─ cliff (~0.1.8)  None
│ ├─ colors (0.x.x)   colors.js (0.6.2-1)
│ ├─ winston (0.6.x)  None
│ │  ├─ eyes (0.1.x)  eyes.js (0.1.8-1)
│ │  ├─ pkginfo (0.3.x)   None
│ │  ├─ request (2.16.x)  node-request (2.26.1-1)
│ │  ├─ colors (0.6.x)colors.js (0.6.2-1)
│ │  ├─ async (0.2.x) node-async (0.2.5-1)
│ │  ├─ stack-trace (0.0.x)   None
│ │  └─ cycle (1.0.x) None
│ └─ eyes (0.1.x) eyes.js (0.1.8-1)
├─ serve-static (~1.2.3)  None
│  ├─ parseurl (1.0.1)None
│  ├─ send (0.4.3)node-send (0.1.4-1)
│  └─ escape-html (1.0.1) None
├─ uuid (~1.4.1)  node-uuid (1.4.0-1)
├─ multiparty (~3.2.9)node-multiparty (2.2.0-1)
├─ pend (~1.1.1)  None
├─ archiver (~0.10.1) None
│  ├─ buffer-crc32 (~0.2.1)   node-buffer-crc32
(0.2.1-1)
│  ├─ lazystream (~0.1.0) None
│  │  └─ readable-stream (~1.0.2) None
│  ├─ lodash (~2.4.1) None
│  ├─ zip-stream (~0.3.0) None
│  │  ├─ buffer-crc32 (~0.2.1)node-buffer-crc32
(0.2.1-1)
│  │  ├─ crc32-stream (~0.2.0)None
│  │  │  ├─ buffer-crc32 (~0.2.1) node-buffer-crc32
(0.2.1-1)
│  │  │  └─ readable-stream (~1.0.24) None
│  │  ├─ deflate-crc32-stream (~0.1.0)None
│  │  │  └─ buffer-crc32 (~0.2.1) node-buffer-crc32
(0.2.1-1)
│  │  ├─ lodash.defaults (~2.4.1) None
│  │  │  ├─ lodash.keys (~2.4.1)  None
│  │  │  │  ├─ lodash.isobject (~2.4.1)   None
│  │  │  │  │  └─ lodash._objecttypes (~2.4.1)None
│  │  │  │  ├─ lodash._shimkeys (~2.4.1)  None
│  │  │  │  │  └─ lodash._objecttypes (~2.4.1)None
│  │  │  │  └─ lodash._isnative (~2.4.1)  None
│  │  │  └─ lodash._objecttypes (~2.4.1)  None
│  │  ├─ readable-stream (~1.0.26)None
│  │  └─ debug (~0.8.0)   node-debug (0.6.0-1)
│  ├─ file-utils (~0.2.0) None
│  │  ├─ minimatch 

Re: [Pkg-javascript-devel] where do I begin? I want to package many node module dependencies for an application

2014-06-27 Thread Emilien Klein
Hi andrewrk,

2014-06-26 22:19 GMT+02:00 Andrew Kelley superjo...@gmail.com:
 Hello pkg-javascript-devel team,

 I am andrewrk from the pkg-multimedia-maintainers team.

 I started packaging Groove Basin - a music player server built with Node.js
 - and now I need to package up all of its module dependencies. These are:
[snip]
 I am ignorant of how this process works. Where do I begin? How can I go
 about doing this? Is there documentation on how to create and submit node.js
 packages to Debian?

A good place to start would be
https://wiki.debian.org/Javascript/Nodejs and its two links providing
more information on the process.

Let us know if you need more information.
   +Emilien
P.S.: I'm assuming you are not subscribed to the
pkg-javascript-devel@l.a.d.o list, hence the CC. Let us know if you
are subscribed though.

___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel


Re: [Pkg-javascript-devel] where do I begin? I want to package many node module dependencies for an application

2014-06-27 Thread Andrew Kelley
On Fri, Jun 27, 2014 at 12:35 AM, Emilien Klein emilien+deb...@klein.st
wrote:

 Hi andrewrk,

 Let us know if you need more information.


A couple questions for you:

1. Should I create ITPs for each and every one of the new modules (about
65)?

2. How does one package up modules that contain C++ code?

For me these are:
https://npmjs.org/package/ws
https://npmjs.org/package/leveldown
https://npmjs.org/package/groove

Related question: both ws and leveldown have a conflicting runtime
dependency on https://npmjs.org/package/nan but this looks like perhaps it
should be a compile-time dependency. Any advice on this?



 P.S.: I'm assuming you are not subscribed to the
 pkg-javascript-devel@l.a.d.o list, hence the CC. Let us know if you
 are subscribed though.


I am now subscribed :-)
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] where do I begin? I want to package many node module dependencies for an application

2014-06-27 Thread Emilien Klein
2014-06-27 17:34 GMT+02:00 Andrew Kelley superjo...@gmail.com:
 On Fri, Jun 27, 2014 at 12:35 AM, Emilien Klein emilien+deb...@klein.st
 wrote:

 Hi andrewrk,


 Let us know if you need more information.


 A couple questions for you:

 1. Should I create ITPs for each and every one of the new modules (about
 65)?

It might not be a strict requirement (some folks don't), but I
consider that to be best practice. It might prevent duplicate work
(assume somebody else works on that package at the same time), and can
be helpful to find other interested Debian contributors, in case your
package gets stuck (happened to me with the Shaarli package for which
I didn't find a mentor to upload and review, a couple of months later
somebody started working on the same package and luckily found my
ITP).

 2. How does one package up modules that contain C++ code?

 For me these are:
 https://npmjs.org/package/ws
 https://npmjs.org/package/leveldown
 https://npmjs.org/package/groove

Do these packages have a Makefile, or some building recipe? If it's
using one of the popular tools, the package helpers should be able to
take care of the building process for you.

 Related question: both ws and leveldown have a conflicting runtime
 dependency on https://npmjs.org/package/nan but this looks like perhaps it
 should be a compile-time dependency. Any advice on this?

What do you mean by conflicting? They depend on a different version of nan?

   +Emilien

___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel


Re: [Pkg-javascript-devel] where do I begin? I want to package many node module dependencies for an application

2014-06-27 Thread Jérémy Lal
Le vendredi 27 juin 2014 à 21:28 +0200, Emilien Klein a écrit :
 2014-06-27 17:34 GMT+02:00 Andrew Kelley superjo...@gmail.com:
  On Fri, Jun 27, 2014 at 12:35 AM, Emilien Klein emilien+deb...@klein.st
  wrote:

  2. How does one package up modules that contain C++ code?
 
  For me these are:
  https://npmjs.org/package/ws
  https://npmjs.org/package/leveldown
  https://npmjs.org/package/groove
 
 Do these packages have a Makefile, or some building recipe? If it's
 using one of the popular tools, the package helpers should be able to
 take care of the building process for you.

Usually c++ node modules use node-gyp, see packages build-depending on
node-gyp to find out about it (reverse-depends -b node-gyp).

Jérémy.



___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] where do I begin? I want to package many node module dependencies for an application

2014-06-27 Thread Andrew Kelley
On Fri, Jun 27, 2014 at 1:39 PM, Jérémy Lal kapo...@melix.org wrote:

 Le vendredi 27 juin 2014 à 21:28 +0200, Emilien Klein a écrit :
  2014-06-27 17:34 GMT+02:00 Andrew Kelley superjo...@gmail.com:
   On Fri, Jun 27, 2014 at 12:35 AM, Emilien Klein 
 emilien+deb...@klein.st
   wrote:

   2. How does one package up modules that contain C++ code?
  
   For me these are:
   https://npmjs.org/package/ws
   https://npmjs.org/package/leveldown
   https://npmjs.org/package/groove
 
  Do these packages have a Makefile, or some building recipe? If it's
  using one of the popular tools, the package helpers should be able to
  take care of the building process for you.

 Usually c++ node modules use node-gyp, see packages build-depending on
 node-gyp to find out about it (reverse-depends -b node-gyp).


Thanks, this is helpful.


So far I have packaged up 3 modules:
http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-findit.git;a=summary
http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-pend.git;a=summary
http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-keygrip.git;a=summary

Any feedback before I continue?
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel