Hi, Le dimanche 21 novembre 2021 à 14:18 +0100, Yadd a écrit : > Le 21/11/2021 à 09:11, Andrius Merkys a écrit : > > > > > I must admit my knowledge of JS packaging lags quite a lot, thus I > > rely > > a lot on tools. I would expect npm2deb to produce initial packaging > > at a > > fair state, and lintian to throw warnings/errors about the "dirty > > work" > > (as opposed to notes which are quite invisible). > >
I have to side with Andrius here: more and more of the JS package fall out of my reach -- notably some of the node-rollup-plugin-* packages. I'm having a though time with packages with subpackages with out-of- this-world version numbers... > > I am aware that npm2deb is not developed by Debian JS Team, thus it > > is > > quite natural it does not follow JS Team policies close enough. > > Maybe it > > should be taken over by Debian, or its usage to do packaging in > > Debian > > be strongly discouraged? (Maybe it is already, only I am not > > aware). > > I just updated npm2deb, however it is a good practice to launch > `lintian-brush`. In addition, npm2deb's agorithm is very > questionable, in particular for the search for reverse dependencies. > I didn't know about lintian-brush. I'll give it a test drive. > I'll try to package my personal tools which permits to fix many > things automatically. The best would to include them in lintian-brush > but sadly I've no talent in Python (all my tools are Perl scripts). For my packages I don't have personal tools, only a personal routine: (1) "lintian -I" to get things right (sometimes adding a --pedantic when I'm feeling in the mood) ; (2) build the source package in a schroot-sbuild-unstable to check I got deps right after the initial round of ; (3) if it's a sensitive package (fragile and important rdeps I know about), I put the binary packages in my local repo, and try to build a random few of the reverse-deps by hand with them ; (4) upload. This isn't perfect: I uploaded a newer node-typescript a few weeks ago and it broke ts-node (which obviously wasn't in the list of rdeps I had checked). I can't update it to a newer upstream which would fix the issue because it has new deps (or deps with newer versions), so I'm mostly waiting for those to clear before I can finally fix it. Cheers, J.Puydt -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
