[Pkg-javascript-devel] Bug#870460: anyone working on npm?

[Jérémy Lal]

2018-04-19 7:57 GMT+02:00 Diane Trout <diane at ghic.org>:

>
> Sure ! You could work on a branch of npm pkg-javascript repository,
> and ask me for reviewing it and merging it. If all goes well, after that
> first
> review, you'll work directly on master branch.
>
>
> Hi
>
> I finally had time to finish producing a hopefully easy to review set of
> patches. (And went through and tried harder to delete packages from the
> tarball that are packaged for Debian.)
>
> I couldn't commit to alioth right now, so I made a personal project for
> npm on salsa.
>
> The branch is intended to be rebased on top of gbp import-orig --uscan.
>
> https://salsa.debian.org/diane/npm/tree/diane-npm-5.7.1-pkg
>

I've moved npm repository to salsa:js-team/npm.git
I quickly reviewed the commits and it is great work, so please do
a merge request and we'll fix what need to be fixed afterwise.


> I was taking longer than npm was releasing new versions so I didn't want
> it to depend on a specific version of npm.
>

Yes, upstream is hard to keep up with, especially since
they often add/remove dependencies.

I've been testing the build by removing all the old npm files and then
> unpacking the new tarball in its place.
>
> rm -rf appveyor.yml AUTHORS bin/ CHANGELOG.md changelogs/ cli.js configure
> CONTRIBUTING.md  doc/ html/ \
> lib/\LICENSE make.bat Makefile  node_modules/ package* README.md  scripts/
> test/ TROUBLESHOOTING.md .pc
> tar xavf ../npm_5.8.0+ds.orig.tar.gz --strip=1
> debuild -S -uc -us -d
> cd ..
> cowbuilder-dist sid build npm_5.8.0+ds-1.dsc
>

I would have advised to use
- in debian/watch, repacksuffix=+ds (check the example in js-team/nodejs)
- then gbp import-orig ../npm_5.8.0+ds.orig.tar.gz
- then gbp buildpackage --ignore-debian-branch
with that default config in ~/.gbp.conf
[DEFAULT]
sign-tags = True
builder = sbuild
postbuild = lintian -I $GBP_CHANGES_FILE && echo "Lintian OK"
[import-orig]
pristine-tar = True

Setting up sbuild almost surely requires to use an apt cache like
apt-cacher-ng,
which you can then setup to be used by both your system and by sbuild (so
packages
don't get downloaded twice).

I added a minimal autopkgtest test that makes sure "npm list" can actually
> run.
>

Good.

Hope that helps. and anything you'd like me to work on next?
>

There is a ton of things to do in the pkg-javascript team.

If you search a more technical task related to npm/nodejs, i'd suggest:

-  look into the possibility for npm to automatically pick up modules in
/usr/lib/nodejs/* when the versions match. That's going to work for modules
that have been properly packaged, installing
/usr/lib/nodejs/<modulename>/package.json
That feature should be optional, like the ruby team did with
rubygems-integration,
through the installation of a npm-integration debian package.

- look into building nodejs in two separates parts: the library and the
executable,
and ship a multiarch libnode module.

- and of course, maintain npm debian package...

Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20180419/c25ca4b9/attachment.html>