Re: Is there any mechanism of Guix analog to, or trick in Guile to imitate Nix flakes?

[Suhail Singh]

rczb <rc-zb@outlook.com> 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 along with specification->package) with
a channels.scm and then doing the build via guix time-machine?

> The lock file is not mandatory. You can delete it whenever you want an
> update, and the next invoking of `nix build` or something on the flake
> directory will just generate a new one that conforms what's written in
> `inputs` while being as up-to-date as possible to the upstream.

How would this be different than updating the channels.scm file?

-- 
Suhail