Hi Martin,

2018-02-14, W. Martin Borgert:
> did the discussion about coffeescript vs ECMA6 already lead to something?

We mentioned it a few times during the weekly meetings we have on
tuesdays. We have been busy lately with the 1.0.0 release!


This is hard for me to estimate the repercussions as I lack good
knowledge of the JS ecosystem. It does not look like a trivial task in
any case :)

I'll try to bring this up next tuesday to see when/if this can be

> In any case, I suggest mass-file RFPs/ITPs for all needed node packages.
> Then package as many as you feel like. Maybe others will help, let's see.
> I cannot promise any help, because I'm already busy with other tasks.
> I recommend to package all node libraries under the umbrella of the
> Debian Javascript Maintainers <pkg-javascript-de...@lists.alioth.debian.org>
> They have their git repo here: https://salsa.debian.org/js-team

That's very nice to know. Thanks! I was afraid I might need to do all
that myself :D

For now, I am focusing in having only the server and worker packages
(without any web ui) updated in debian with the latest upstream release.
There is a small limitation in pybuild regarding building multiple
binary packages from the same source package (each located in
subdirectories). I talked with p1otr on #debian-python and he told me he
may have a fix uploaded soon(tm).

In the meantime, I am struggling to make the tests run and docs build
with only debian dependencies.

Once this is done, I will work on web ui packages. Hopefully,
buildbot-www* packages will have gotten rid of some dependencies which
would make debian integration easier. I'll surely shime in #debian-js to
ask for guidance.



Reply via email to