Hi guix, I was wondering if a node-team would be useful to make the work towards making a few applications available in Guix.
It's been quite some time that 68941 is ready but forgotten. Based on this patch series, I'm now able to build a node-tape-bootstrap with minimal missing dependencies to make the process fully bootstrapped (concat-stream, tap, libtap, es-value-fixtures). So I can send : - a rebased 68941 v3, probably moving all those packages and then some in a new node-bootstrap.scm - a patch series completing those up to node-tape with those few missing bootstrapped dependencies, probably bootstrap libtap and es-value-fixtures along the way. I use an opiniated trick here that would require some review, the same one as in 67902 that had the same fate (patch series ready but unreviewed and forgotten). We also need some fixes to the build-system there. >From there, the path seems clear to me : - extend the node-build-system to a node-workspace-build-system to be able to package tap without requiring 2k+ lines. I've done that for a rust-build-system but lost the progress since, but I know it's doable. - build node-tap-bootstrap on node-tape-bootstrap - rebuild a node-tape with node-tap-bootstrap - rebuild a node-tap with node-tap - port typescript build from guixrus in a new node-build.scm or node-typescript.scm These are the minimal building blocks to start being able to package some final-user things. My final goal is a zotero-translation-server sans aws-sdk. I think this is doable but I need some foresight on how this can happen (i.e. Would I tackle that alone and should I eventually setup GPG or (my preference) can I do that in close collaboration with a new node-team member ?) -- Best regards, Nicolas Graves
