From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: ’guix package --export-manifest’ using ’@version’?
Date: Thu, 07 Jul 2022 17:13:43 +0200 [thread overview]
Message-ID: <8735fdymzc.fsf@gnu.org> (raw)
In-Reply-To: <86pmihoyb3.fsf@gmail.com> (zimoun's message of "Thu, 07 Jul 2022 15:19:12 +0200")
zimoun <zimon.toutoune@gmail.com> skribis:
> On Thu, 07 Jul 2022 at 09:57, Ludovic Courtès <ludo@gnu.org> wrote:
[...]
>> 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:
Oh sorry, I had misunderstood your comment.
The “@X.Y” bit is added only when necessary to disambiguate the package
spec. So with today’s Guix, we have:
--8<---------------cut here---------------start------------->8---
$ guix shell guile --export-manifest
;; What follows is a "manifest" equivalent to the command line you gave.
;; You can store it in a file that you may then pass to any 'guix' command
;; that accepts a '--manifest' (or '-m') option.
(specifications->manifest (list "guile"))
$ guix shell guile@2.2 --export-manifest
guix shell: warning: ambiguous package specification `guile@2.2'
guix shell: warning: choosing guile@2.2.7 from gnu/packages/guile.scm:250:2
guix shell: warning: ambiguous package specification `guile@2.2'
guix shell: warning: choosing guile@2.2.7 from gnu/packages/guile.scm:250:2
;; What follows is a "manifest" equivalent to the command line you gave.
;; You can store it in a file that you may then pass to any 'guix' command
;; that accepts a '--manifest' (or '-m') option.
(specifications->manifest (list "guile@2.2.7"))
$ guix shell guile@2.0 --export-manifest
;; What follows is a "manifest" equivalent to the command line you gave.
;; You can store it in a file that you may then pass to any 'guix' command
;; that accepts a '--manifest' (or '-m') option.
(specifications->manifest (list "guile@2.0"))
--8<---------------cut here---------------end--------------->8---
In these cases, we cannot omit the “@X.Y” bit because the manifest would
then designate something different.
Does that make sense?
Ludo’.
next prev parent reply other threads:[~2022-07-07 15:14 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
2022-07-07 15:13 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735fdymzc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--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.