Re: Help adding a graph backend

As the message says, use ./configure --localstatedir=/var :) Le 10 février 2023 04:10:02 GMT+01:00, Kyle Andrews a écrit : > >Dear Guix, > >I am not very comfortable editing Guix source code. However, I would >very much like to add a new backend for `guix graph`. Right now guix >graph description

Help adding a graph backend

Dear Guix, I am not very comfortable editing Guix source code. However, I would very much like to add a new backend for `guix graph`. Right now guix graph descriptions can only be exported into special purpose tools like graphviz, D3, and cypher. I would like to add a fourth option which would s

guix build -S 💛 --with-branch

Hi Guixers, Just opening this thread for us to brainstorm how we can improve the symbiosis between guix build -S and --with-branch. >From a #guix irc conversation earlier today with civodul: jgart: What do people think of having a guix clone command that passes the result of (-> network-manage

Re: What's the state of (guix build download-nar)?

Maxim Cournoyer writes: > Hi, > > Ludovic Courtès writes: > >> Hi Chris! >> >> Christopher Baines skribis: >> >>> I guess this raises two things in my mind. I'm not sure this'll work >>> well given the not so recent changes to ci.guix.gnu.org. This module >>> looks to rely on gzipped or uncomp

Re: What's the state of (guix build download-nar)?

Hi, Ludovic Courtès writes: > Hi Chris! > > Christopher Baines skribis: > >> I guess this raises two things in my mind. I'm not sure this'll work >> well given the not so recent changes to ci.guix.gnu.org. This module >> looks to rely on gzipped or uncompressed nars. I'm not sure uncompressed >

Discussion notes on releases and branches

Attached are the notes of our discussion at the Guix Days concerning releases, branches, teams and related matters. Andreas Releases, branches, teams Problem: It took us 1.5 years for the last release, and the coreupdates branch has been open for at least as much. RELEASES Why do we make rele

Re: configurable guile backtrace in builder

> How about passing #:env-vars '(("COLUMNS" . "200")) to > ‘gexp->derivation’ (in the build system), or adding a phase that sets > that environment variable? i assume printed guile backtraces should not be part of the normal output of any package. and then why not introduce an env variable (or