From: SailSXiao <sail_s_xiao@163.com>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Is there any mechanism of Guix analog to, or trick in Guile to imitate Nix flakes?
Date: Tue, 28 May 2024 00:34:21 +0800 [thread overview]
Message-ID: <-xnt8i2-sim3wehz5tn4k0kr7gmb88fftln6y8-d2re63u23t10-hgax49-xi993k7pdmp1hfqx9lcvfvc1-o3qpt4-uheq9n-2af1is-6gefyy-28qm1b-kvbn4s-v2ea5l-py3tmuctmpf2-xu0j70-9vqeu1.1716825659565@email.android.com> (raw)
GNU Guix is known as one of the most insistent package managers on
reproducibility, the same as Nix, from which Guix was deeply inspired.
However, while the two programs share most of their philosophies, I
couldn't see something like flakes in Guix. I know Guix has
descriptions and manifests, or integrated inferiors, which guarantee
the exactness of building of a package set. But all these mechanisms
point directly to the precise references ("guix.git" with a commit
hash), rather than separate the unlocked references ("nixpkgs/master"
in flake.nix) from the locks (flake.lock), which allows imperative
upgrade for a specific workspace.
So, is there any mechanism of Guix analog to, or trick in Guile to
imitate the functionalities of flakes? Or is there a possibility for
this? I have merely skimmed R7RS, and know little about the Guile
implementation, but just impressed by the generality of the language.
So I wonder if this can be done provided a much more powerful backend
than that of Nix.
next reply other threads:[~2024-05-27 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 16:34 SailSXiao [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=-xnt8i2-sim3wehz5tn4k0kr7gmb88fftln6y8-d2re63u23t10-hgax49-xi993k7pdmp1hfqx9lcvfvc1-o3qpt4-uheq9n-2af1is-6gefyy-28qm1b-kvbn4s-v2ea5l-py3tmuctmpf2-xu0j70-9vqeu1.1716825659565@email.android.com \
--to=sail_s_xiao@163.com \
--cc=help-guix@gnu.org \
/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.