all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Suhail Singh <suhailsingh247@gmail.com>
To: rczb <rc-zb@outlook.com>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
	 "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Is there any mechanism of Guix analog to, or trick in Guile to imitate Nix flakes?
Date: Sun, 16 Jun 2024 11:00:01 -0400	[thread overview]
Message-ID: <87cyohexvy.fsf@gmail.com> (raw)
In-Reply-To: <ME3P282MB3920CE3E632464C3AC0D1050F8C62@ME3P282MB3920.AUSP282.PROD.OUTLOOK.COM> (rczb's message of "Tue, 11 Jun 2024 01:54:45 +0800")

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


  reply	other threads:[~2024-06-17 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 16:37 Is there any mechanism of Guix analog to, or trick in Guile to imitate Nix flakes? ‪肖 海帆‬
2024-06-04 18:03 ` Simon Tournier
2024-06-10  4:41   ` Abbé
2024-06-10 17:54   ` rczb
2024-06-16 15:00     ` Suhail Singh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-27 16:34 ‪‪SailSXiao‬‬

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cyohexvy.fsf@gmail.com \
    --to=suhailsingh247@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=rc-zb@outlook.com \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.