From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: ’guix package --export-manifest’ using ’@version’?
Date: Thu, 07 Jul 2022 15:19:12 +0200 [thread overview]
Message-ID: <86pmihoyb3.fsf@gmail.com> (raw)
In-Reply-To: <87h73t1hke.fsf@gnu.org>
Hi,
On Thu, 07 Jul 2022 at 09:57, Ludovic Courtès <ludo@gnu.org> wrote:
> (Nitpick: it *is* stateless, in the sense that it only depends on Guix
> itself, not on the state of the machine where it is being run.)
I will not argue about what we call state here. :-)
> ‘--export-manifest’ emits a comment (shown above) explaining that the
> manifest is symbolic and that one needs channel info to replicate the
> exact same environment.
I do not understand what you mean by «symbolic» here.
> It is a departure from traditional package managers, and admittedly
> surprising to newcomers. However, my take on this is that we should be
> very upfront about symbolic vs. exact reproducibility. We would muddy
> the waters if we gave version strings the same importance as in other
> tools, when we know that a version string means very little.
I miss about what you disagree because «We would muddy the waters if we
gave version strings the same importance as in other tools, when we know
that a version string means very little.» is the exact root of my
comment.
By returning,
(specifications->manifest
(list "python" "python-numpy"))
or
(specifications->manifest
(list "python@3.8" "python-numpy@1.17"))
depending on the current Guix is just doing that: «muddy the waters».
Instead, I think ’--export-manifest’ should *always* return:
(specifications->manifest
(list "python" "python-numpy"))
without ’@x.y.z’. Other said, be in agreement with the comment:
;; This is "symbolic": it only specifies
;; package names. To reproduce the exact same profile, you also need to
;; capture the channels being used, as returned by "guix describe".
and not sometimes ’package name’ and sometimes ’package name + version’;
as if version string has a special meaning.
To be honest, I do not understand: on one hand, we are advocating that
version string is not enough for reproducibility. On the other hand, we
output version string with a comment «version string is useless, you
need a channel file for replicating».
Since I am missing a point, could you explain more?
Cheers,
simon
next prev parent reply other threads:[~2022-07-07 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 19:00 ’guix package --export-manifest’ using ’@version’? zimoun
2022-07-07 7:57 ` Ludovic Courtès
2022-07-07 13:19 ` zimoun [this message]
2022-07-07 15:13 ` Ludovic Courtès
2022-07-07 16:53 ` zimoun
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=86pmihoyb3.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).