guix build <package> will output all the store names for the outputs of <package> (usually only one). The hash in the directory names is what you want as the narinfo filename.
Le 26 août 2020 12:12:44 GMT-04:00, "Dr. Arne Babenhauserheide" <arne_...@web.de> a écrit : > >Julien Lepiller <jul...@lepiller.eu> writes: > >> I suppose, but that's going to be a bit of work. I'm not very >knowledgeable on this part of guix. I think you'll need to generate a >narinfo and a nar for each store item you want to be available. Maybe >you can run guix publish locally and mirror the files it serves on your >server? > >That sounds like a viable option. > >> You'll need to publish /<store hash of output>.narifo and the other >files it references (the nar archives themselves). > >So I only need a way to get all the hashes referenced for a given >package. Do you know the command for that? > >> So you'd download them from localhost and send them to your server. >Your guix daemon must trust the builder's public key, or the substitute >will not be downloaded. >> >> Le 26 août 2020 10:56:26 GMT-04:00, "Dr. Arne Babenhauserheide" ><arne_...@web.de> a écrit : >>>Julien Lepiller <jul...@lepiller.eu> writes: >>>> The best would be to run "guix publish" on your server, as it will >>>allow others to use your server as a substitute server, instead of >>>having to manually download archives of the package and dependencies. >>>Thank you for your answer! >>> >>>Is it possible to do the equivalent of guix publish on a dumb server? >>> >>>The webhosts I have are pretty dumb servers that definitely have no >>>Guix, and I have no root-access (and currently don’t want it, because >I >>>don’t like the maintenance burden that comes with it). > > >-- >Unpolitisch sein >heißt politisch sein >ohne es zu merken
