Hi, (I'm not subscribed, so please CC: me)
Recent versions of openQA make use of shepherd.js, which the openQA build system gets in the form of a single file, built output, from here: https://shepherdjs.dev/dist/js/shepherd.js by using Mojolicious AssetPack[1]. To avoid such build-time downloads I'm currently editing the assetpack configuration file to point it at locally available copies of the files, mostly by depending on debian packages that include the same or similar versions of the files, and pointing symlinks at those files so that Assetpack can find them. This is a bit of a hack, so I'd be happy to know if there's a better way. You can find shepherd.js here: https://shepherdjs.dev/ https://github.com/shipshapecode/shepherd which is not yet packaged, so I'm now wondering what is the best thing to do in order satisfy the new dependency, and thus to be able to package recent openQA. Given that it is BSD licensed, perhaps it would be acceptable to simply include the generated file in my source, and document where it came from, but that strikes me as sub-optimal, even if allowed. Presumably one could either package it directly, or via npm somehow. Is one approach considered better than the other? Is filing an RFP the right next step for this? I'm happy to give packaging it a go myself, if someone's willing to provide me with hints about how best to go about it. In that case I'd hope to hand the package over to the Javascript team afterwards, since I have no experience with packaging Javascript and my interest in the package is only in it's ability to satisfy this dependency. Cheers, Phil. [1] https://metacpan.org/dist/Mojolicious-Plugin-AssetPack -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/ http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY
signature.asc
Description: PGP signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
