Re: Finding the store path of a package

>Ludovic Courtès wrote: >> Yes. In the presence of grafts, run “guix build PKG”. That always >> gives you the store file name of PKG, 100% reliable! >At the cost of a few hours of CPU time, in the worst case. >> I regularly do things like: >> >> ls $(guix build PKG)/bin >> find $(guix build P

Re: Finding the store path of a package

Hi Ludo, > Why #:graft? #f? Because if you enable graft, you’ll potentially have > to build/download the thing, and that wouldn’t buy you anything because > the set of file names is the same in the grafted package. Four weeks later: this mostly works, but sometimes fails (by downloading/building

Re: Finding the store path of a package

Hi Ludo, > Here’s an example of how to do that: Works fine, thanks! > Why #:graft? #f? Because if you enable graft, you’ll potentially have > to build/download the thing, and that wouldn’t buy you anything because > the set of file names is the same in the grafted package. OK, so that's the se

Re: Finding the store path of a package

Hi Konrad, Konrad Hinsen skribis: >> Yes. In the presence of grafts, run “guix build PKG”. That always >> gives you the store file name of PKG, 100% reliable! > > At the cost of a few hours of CPU time, in the worst case. > >> I regularly do things like: >> >> ls $(guix build PKG)/bin >> f

Re: Finding the store path of a package

Hi Simon, > On a side note, Ricardo did recently some stuff as UI for packages, > > > Looks good! My project has a lot of overlap, except that it is very intentionally not based on Web te

Re: Finding the store path of a package

Hi Konrad, On Mon, 22 Mar 2021 at 08:39, Konrad Hinsen wrote: > Background: I am working on a interactive UI for running reproducible > computations via Guix: > > https://github.com/khinsen/guix-gtoolkit/ > > I'd like to implement (1) browsing package contents ("what exactly do I > get by addi

Re: Finding the store path of a package

Hi Ludo, > Yes. In the presence of grafts, run “guix build PKG”. That always > gives you the store file name of PKG, 100% reliable! At the cost of a few hours of CPU time, in the worst case. > I regularly do things like: > > ls $(guix build PKG)/bin > find $(guix build PKG) -name … What I

Re: Finding the store path of a package

Hi! Konrad Hinsen skribis: >>> does “guix build -n” fit your use-case? >> >> Checking... yes! I hadn't even considered using "build" when building is >> exactly what I do not want to happen. But yes, it works just fine. > > Not quite: > > $ guix build -n zziplib > substitute: > /gnu/store/pwcp

Re: Finding the store path of a package

Hi, In addition, I am also lost with this sequence: 1. dry-run openmpi list dependencies 2. do the wrong thing with the REPL 3. garbage collect 4. redo the dry-run and now the dependencies are not listed Sorry Konrad, ’package-output’ is definitively wrong. Worse, the items listed in the f

Re: Finding the store path of a package

Hi Simon, >> does “guix build -n” fit your use-case? > > Checking... yes! I hadn't even considered using "build" when building is > exactly what I do not want to happen. But yes, it works just fine. Not quite: $ guix build -n zziplib substitute: /gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash

Re: Finding the store path of a package

Hi Simon, > does “guix build -n” fit your use-case? Checking... yes! I hadn't even considered using "build" when building is exactly what I do not want to happen. But yes, it works just fine. > Well, ’package-output’ in (guix packages) is what you need, I guess. And that works just fine as wel

Re: Finding the store path of a package

Hi Konrad, On Wed, 17 Mar 2021 at 18:55, Konrad Hinsen wrote: > I wonder if there is a straightforward way to find the store path > corresponding to a package, assuming that the package actually is in the > store. I don't care if it's done via the CLI or via Guile code. does “guix build -n” fi

Finding the store path of a package

Dear Guix experts, I wonder if there is a straightforward way to find the store path corresponding to a package, assuming that the package actually is in the store. I don't care if it's done via the CLI or via Guile code. Use case: Looking at the files inside a package. What I do now is "ls /gnu/