#Guix packagers: you may like these new REPL commands to inspect a package’s configure flags, phases, etc. 👇
https://guix.gnu.org/manual/devel/en/html_node/Using-Guix-Interactively.html
#Guix packagers: you may like these new REPL commands to inspect a package’s configure flags, phases, etc. 👇 13 comments
@csepp The answer is twofold: (1) providing concise ways to express things packagers may want to do, and (2) presenting data in a human-friendly way (lowering gexps and pretty-printing the result). One can still do “,pp (package-arguments grep)” but that’s less convenient. See https://issues.guix.gnu.org/67489 for a discussion. @civodul The problem is that this makes hard to use these in scripts. I ran into exactly this issue when I was writing my MirageOS importer (which I promise I'm gonna try upstreaming during the holidays 😅). I needed to build a package that just ran mirage configure and use the dune config file from it to get the dependency list and call the opam importer, which then generated the code. @civodul Maybe this is a too far reaching problem, but: if the issue is that the string serializations of packages are not nice to read, why not make Guile serialize things nicely by default? @csepp This is meant as a handy interface to inspect packages. Doing the same in a script is ~10 lines of code: But it’s not so useful: in a script, you’d rather call ‘package-arguments’ and preserve gexps as is instead of lowering them, or you’d lower the whole package. @janneke Currently you have to explicitly do (%current-system "i586-gnu") beforehand. @sharlatan There are situations where having ‘guix repl’ load stuff upfront is not desirable (I can’t recall the details off the top of my head). |
@civodul 😍😍😍😍💜💜💜💜💜