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

[Emilien Klein]

2014-06-27 17:34 GMT+02:00 Andrew Kelley <superjoe30 at gmail.com>:
> On Fri, Jun 27, 2014 at 12:35 AM, Emilien Klein <emilien+debian at 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