From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 74015@debbugs.gnu.org
Subject: bug#74015: 'guix shell --export-manifest' fails for some transformations
Date: Sun, 10 Nov 2024 14:06:16 +0100 [thread overview]
Message-ID: <87serzxmpj.fsf@gmail.com> (raw)
In-Reply-To: <87v7wvwc6t.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 10 Nov 2024 12:38:50 +0100")
Hi,
On Sun, 10 Nov 2024 at 12:38, Ludovic Courtès <ludo@gnu.org> wrote:
>> $ guix shell -m manifest.scm --export-manifest
>
> ‘--export-manifest’ is meant to “translate” a command line, which it can
> do faithfully; there’s no way it could possibly “recreate” what
> ‘manifest.scm’, which may contain arbitrary Scheme code (and someone who
> already has a ‘manifest.scm’ file probably doesn’t need
> ‘--export-manifest’).
Yes, one might need. :-)
As I explained: « That’s annoying in some context as “guix pack
--save-provenance” [1]. Even, it defeats the idea of a self-contained
reproducible binary container. »
For sure, I understand it’s hard to capture this kind of transformation.
Still, an improvement appears to me possible (see below).
1: https://hpc.guix.info/blog/2021/10/when-docker-images-become-fixed-point
> It’s necessarily a lossy process.
This is where I disagree. :-) I mean, yes I agree that building
profile/manifest is somehow a lossy process because some Scheme is
potentially evaluated on the road. However, I am proposing: Aside the
profile ’manifest’ file (lossy process), we could store all the
manifests provided by the command line. Something as:
/gnu/store/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-profile/manifest
/gnu/store/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-profile/manifest.orig1
/gnu/store/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-profile/manifest.orig2
…
where manifest.orig1 and manifest.orig2 are the copy of files ’foo.scm’
and ’bar.scm’ from:
-m foo.scm -m bar.scm
This way, the option --export-manifest could be improved, eventually.
In other word, I think that saving as-is the manifests costs almost
nothing and it paves the way to more robust self-contained binary packs.
Well, maybe this extra work could be only done when there is an option
’--save-provenance’ applied.
> I would close it as not-a-bug; WDYT?
I still think it’s a feature that it’s possible to improve.
Cheers,
simon
next prev parent reply other threads:[~2024-11-10 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 17:08 bug#74015: 'guix shell --export-manifest' fails for some transformations Simon Tournier
2024-11-10 11:38 ` Ludovic Courtès
2024-11-10 13:06 ` Simon Tournier [this message]
2024-11-12 15:33 ` Suhail Singh
2024-11-16 7:20 ` Simon Tournier
2024-11-17 19:05 ` Suhail Singh
2024-11-20 10:29 ` Ludovic Courtès
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=87serzxmpj.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=74015@debbugs.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).