Hi Gunnar, Sorry for the delay; I've done more work on the package, but I'm extremely busy at the moment so updates/responses may take a while. The current version fixes a lot of issues but isn't ready for inclusion in Debian yet.
> Ugh. The whole NodeJS ecosystem makes me shiver :-( Agreed. I've been working on packaging dependencies individually when I can, apparently 5 lines of code is enough to warrant an NPM package... > That is also something that cannot be done; packaging software cannot > depend on network connectivity (not even initiate network > connections). The dependencies must be somehow build-depended upon; in > the (ugliest, worst) case you could patch your sources to include the > packages to fulfill this... But I doubt the ftp-masters will approve > of it. I've done this to make the package build successfully, but I'm working with the pkg-javascript group on getting the non-library dependencies packaged independently. Libraries missing from Debian should be OK (using https://packages.debian.org/source/sid/netdata as an example) but build system tools are a bit much. I wrote a basic Makefile to replace upstream's Gulp build system, which helped a lot, but webpack+babel is unavoidable so I'm working on that project at the moment. > We have to ship sources for every piece of software. You don't need to > separate them as long as you provide all the sources and can *prove* > they can be amalgamated to the identical "binary" you are > shipping. That's not a trivial thing, sadly :( Fortunately, the amalgamation is a step in upstream's build process; the bundled libraries are included in source form. The new DSC URL is: https://mentors.debian.net/debian/pool/main/r/rainloop/rainloop_1.11.1-1.dsc I think I've fixed all of the major issues with the package other than the bundled build tools. I'll update the copyright file once that's done and I find out what will still need to be bundled. Please let me know if there's anything else I'm missing. Sincerely, Daniel Ring
