From: Stephen Scheck <singularsyntax@gmail.com>
To: raingloom <raingloom@riseup.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Build determinism, dependency granularity, and dependency scope
Date: Fri, 27 Nov 2020 13:38:41 -0500 [thread overview]
Message-ID: <CAKjnHz11Dz2gg+Hm5O7p2P3+daDnPNor7j4WEwfZ61WwNpB-RQ@mail.gmail.com> (raw)
In-Reply-To: <20201125233905.11206dee@riseup.net>
On Wed, Nov 25, 2020 at 10:52 PM raingloom <raingloom@riseup.net> wrote:
>
> Multiple versions leads to more maintenance burden and a bigger store.
>
That is true, but IMO with Guix's focus on build determinism and
repeatability, it's a price that must be paid.
> But I admit I didn't really investigate which exact module versions
> Yggdrasil is compatible with.
>
As an end-user, if I'm installing the Yggdrasil package with a specific
version, say 0.3.15, that corresponds to a specific Git commit tag, I want
that package to maintain fidelity with the dependency versions locked down
by the upstream project maintainers. As it stands, the Guix dependency
declaration mechanism is lossy, flattening out dependencies to a single
global scope which all packages in a profile must assume.
Unfortunately, for me, that really limits its usefulness.
next prev parent reply other threads:[~2020-11-27 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 21:20 Build determinism, dependency granularity, and dependency scope Stephen Scheck
2020-11-25 22:39 ` raingloom
2020-11-27 18:38 ` Stephen Scheck [this message]
2020-11-25 23:15 ` Leo Famulari
2020-11-27 19:08 ` Stephen Scheck
2020-11-28 2:30 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKjnHz11Dz2gg+Hm5O7p2P3+daDnPNor7j4WEwfZ61WwNpB-RQ@mail.gmail.com \
--to=singularsyntax@gmail.com \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).