rczb writes:
> During evaluation, Nix will generate a JSON file named `flake.lock`,
> which stores the exact revisions of the dependencies, just like the
> output of `guix describe -f channels`.
How would this be different from using, in Guix, say, a manifest file
(using the specification syntax
Tomas Volf <~@wolfsden.cz> writes:
> Thank you very much, I can just stuff it into .guile for now.
For the benefit of others on the mailing list, something like the below
in .guile ensures that the customization runs only for guix repl:
#+begin_src scheme
(when (equal? (module-name (current-mo
Marek Paśnikowski writes:
> I would not be able to go this far without using random elements found
> in other Go packages. It is unfortunate, that the build system
> reference page is missing some key concepts in the Go process.
> https://guix.gnu.org/manual/en/html_node/Build-Systems.html
Plea
Tomas Volf <~@wolfsden.cz> writes:
> Currently Guix uses *intersection* of keys from all parents. I would
> like to suggest modifying the check to use an *union* of:
>
> 1. *Intersection* of keys from all parents (the current logic).
> 2. Keys listed in $GUIX_AUTHENTICATE_EXTRA_KEYS.
>
> (and, if
Tomas Volf <~@wolfsden.cz> writes:
> In other words, the additional whitelisted keys are added to the set
> of valid keys for a commit only if the key material exists on the
> keyring branch.
Makes sense.
--
Suhail
