On 2025-02-13 14:53, Jelle Licht wrote: > Hi Nicolas, > > Nicolas Graves <ngra...@ngraves.fr> writes: > >> Hi guix, >> >> I was wondering if a node-team would be useful to make the work towards >> making a few applications available in Guix. > > Agreed! I've slightly broadened the scope to JavaScript packages in > general for new team at https://issues.guix.gnu.org/76268. > > A nonexhaustive list of things that could already be rolled into the node-team > branch going forward: > > - helper methods to package 'simple' packages: > https://issues.guix.gnu.org/68941 > - import/npm-binary: Handle vector of licenses: > https://issues.guix.gnu.org/76220 > - Replace (guix build json) with (json) in node build system: > https://issues.guix.gnu.org/74900 > - Bumping node-lts in guix from 22.12.0 to 22.14.0 > (no patch yet, still building locally)
I should send my other patches then, I do have 2/3 patches for the build-system too. Will do that this evening (European time) > >> [snip] >> 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. > > What is the trick you refer to in https://issues.guix.gnu.org/67902? Instead of defining -bootstrap version of a lot of packages, I define them in their final version, then when building the bootstrapped "big" package (phpunit for PHP, note-tape for Javascript), I recursively rewrite its inputs to add a #:tests? #f flag and empty their native-inputs. So instead of having (written pkg-bootstrap) -> big-pkg -> pkg, we have (compilation-time calculated pkg-bootstrap) -> big-pkg -> pkg. This is a hack because it's less robust than defining all -bootstrap packages, but in both cases it might save more than 1k lines to maintain, and it's more pleasant to work with (but also demands more rebuilds, since a single change often demands to rebuild the whole chain). >> [snip] >> >> 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 ?) > > Seems like it should at least be shepherded and tested by this team indeed. > > Kind regards, > Jelle > -- Best regards, Nicolas Graves
