Hi all, I needed npm-groovy-lint on an airgapped system today, and while I was able to manually copy all of the 86 dependencies to that system, I wondered if it was possible to package it in OBS. I got it building and it seems to be working, i.e. I could lint a Jenkinsfile with it. But it is a mess.
https://build.opensuse.org/project/show/home:ojkastl_buildservice:npm_packag...
I mostly got it building by copying things from some of the recently updated packages in devel:languages:nodejs, but as most of the packages in that project are > 2 years old I was wondering: There seem to be some packages that are still being maintained, but to me it looks like packaging npm packages is abandoned? Especially as each package seems to bring along all of its dependencies, but (AFAICS) with a subtle difference to golang and the vendoring there: With go packages the vendoring is only used during build, while the dependencies for npm packages seem to be used at runtime, not only for building the package. Hence each and every funny file in each of the dependencies spits out a warning when building the RPM package. Is it worth it to submit my package? Is there a better approach to packaging things like npm-groovy-lint? An automated approach for packaging all of the dependencies? (Just joking...) In other words: If someone wants to have a look and has hints and tips for improving the packaging, fire away... :-) Have a nice day, everyone! Kind regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537