Hi Ricardo, Ricardo Wurmus <[email protected]> writes:
> Sergio Pastor Pérez <[email protected]> writes: > >> I've been informed by some members of the Nix community that >> Zulip has >> been packaged from source in this repository[4]. I've not done >> yet an >> in-depth review of the repository. For now, I didn't see >> anything that >> would make me think it's not packageable in Guix. Maybe some of >> our more >> experienced Python users can take a quick look. >> >> [4] https://git.afnix.fr/nix-zulip/nix-zulip > > This is why we wouldn't be able to package it for Guix: > > https://git.afnix.fr/nix-zulip/nix-zulip/src/branch/main/nix/packages/zulip-server/default.nix#L71 > > --8<---------------cut here---------------start------------->8--- > pnpmDeps = pnpm.fetchDeps { > inherit (finalAttrs) pname version src; > fetcherVersion = 2; > hash = "sha256-Bvl8viPDyi3cla1zL87mUjIavCqaWNRLKfoELqufmj8="; > }; > --8<---------------cut here---------------end--------------->8--- > > This is a trick similar to what we're using for the > bazel-build-system in the Guix Science channel. Roughly speaking > this runs "npm install" outside of the build, bundles up the > resulting massive blob of JavaScript in various states of > illegibility, and treats that bundle as an input with a known > hash. Thanks for looking into this. That's very unfortunate, I wonder if this is a red line for Guix? Do you know if things such as Forgejo[1] suffer from the same problem? Or other infrastructure that Guix has been okay with, even though it's currently unrealistic to package? [1] https://forgejo.org Best regards, Sergio
