[Pkg-javascript-devel] RFP shepherd.js, maybe?

[Jérémy Lal]

On Wed, Apr 13, 2022 at 6:32 PM Philip Hands <phil at hands.com> wrote:

> 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?
>

Package shepherd from git source.


> Is filing an RFP the right next step for this?
>

Not sure about that. RFP looks sometimes like a request to be forgotten.

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.
>

Direct dependencies (as in package.json) miss smoothscroll-polyfill.
But this could be patched away, since modern browsers do have smoothscroll.

Build (devDependencies) dependencies are more complicated.
A lot of them are missing, but it seems the ones needed to build the dist
file are
available in Debian. The missing ones might be for the test suite.

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.
>

The more you do, the more likely you'll get something.

We can help in the process, though.

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