From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxime Devos <maximedevos@telenet.be>, 56114@debbugs.gnu.org
Subject: bug#56114: Guix does not have a documented general and practical procedure for lowering a single lowerable object to the /gnu/store/... string.
Date: Mon, 04 Jul 2022 17:43:22 +0200 [thread overview]
Message-ID: <87y1x8nasl.fsf@gmail.com> (raw)
In-Reply-To: <87edz1zzrz.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 03 Jul 2022 22:50:40 +0200")
Hi,
If I read correctly, this snippet from the manual,
>> scheme@(guile-user)> ,run-in-store (package->derivation hello)
>> $1 = #<derivation /gnu/store/...-hello-2.9.drv => ...>
becomes
scheme@(guile-user)> ,lower hello
and this snippet,
> scheme@(guix-user)> ,run-in-store (lower-object (plain-file "foo" "bar"))
> $15 = "/gnu/store/798sxvdgr0680czdggbls7rd3sfwk2yx-foo"
becomes
scheme@(guile-user)> ,build (plain-file "foo" "bar")
However, note that,
--8<---------------cut here---------------start------------->8---
scheme@(guix-user)> ,build (plain-file "foo" "bar")
$1 = "/gnu/store/798sxvdgr0680czdggbls7rd3sfwk2yx-foo"
scheme@(guix-user)> ,lower (plain-file "foo" "bar")
$2 = "/gnu/store/798sxvdgr0680czdggbls7rd3sfwk2yx-foo"
--8<---------------cut here---------------end--------------->8---
which is confusing, especially when,
--8<---------------cut here---------------start------------->8---
scheme@(guix-user)> ,lower (mixed-text-file "foo" "bar")
$6 = #<derivation /gnu/store/40982nzm6c7n4yawvs3m39k313jsrl80-foo.drv => /gnu/store/raihpcxdz6wmdpyj67bwd4bjk02xq0x3-foo 7f6f9bc5cd20>
scheme@(guix-user)> ,build (mixed-text-file "foo" "bar")
$7 = "/gnu/store/raihpcxdz6wmdpyj67bwd4bjk02xq0x3-foo"
--8<---------------cut here---------------end--------------->8---
The issue – unrelated to the nice patch – is a potential “inconsistency”
between ’<plain-file>’ and ’<computed-file>’; ’plain-file’ refers to
’text-file’ and ’mixed-text-file’ refers to ’text-file*’; and both are
really different despite close names around. :-)
Maybe the docstring of ’plain-file’ and of ’mixed-text-file’ could be
extended. For instance,
--8<---------------cut here---------------start------------->8---
(define (plain-file name content)
"Return an lowered object representing a text file called NAME with the given
CONTENT (a string) to be added to the store.
This is the declarative counterpart of 'text-file'."
--8<---------------cut here---------------end--------------->8---
--8<---------------cut here---------------start------------->8---
(define* (mixed-text-file name #:key guile #:rest text)
"Return an object representing store file NAME containing TEXT. TEXT is a
sequence of strings and file-like objects, as in:
(mixed-text-file \"profile\"
\"export PATH=\" coreutils \"/bin:\" grep \"/bin\")
This is the declarative counterpart of 'text-file*' but note that a
'computed-file' object is returned."
--8<---------------cut here---------------end--------------->8---
> diff --git a/guix/monad-repl.scm b/guix/monad-repl.scm
> index aefabdeebb..15c10efe01 100644
> --- a/guix/monad-repl.scm
> +++ b/guix/monad-repl.scm
> @@ -1,5 +1,5 @@
All LGTM.
> +(define* (evaluate/print-with-store mvalue #:key build?)
> + "Run monadic value MVALUE in the store monad and print its value."
I do not know if it makes sense to have a list of monadic values,
allowing something like:
,build hello coreutils
Cheers,
simon
next prev parent reply other threads:[~2022-07-04 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 21:01 bug#56114: Guix does not have a documented general and practical procedure for lowering a single lowerable object to the /gnu/store/... string Maxime Devos
2022-07-03 20:50 ` Ludovic Courtès
2022-07-04 15:43 ` zimoun [this message]
2022-07-04 20:13 ` Ludovic Courtès
2022-07-04 21:59 ` zimoun
2022-07-05 7:57 ` Ludovic Courtès
2022-07-05 10:13 ` zimoun
2022-07-10 20:03 ` Joshua Branson via Bug reports for GNU Guix
2022-07-15 15:41 ` Ludovic Courtès
2022-07-19 14:10 ` Maxime Devos
2022-07-07 22:25 ` jbranso--- via Bug reports for GNU Guix
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=87y1x8nasl.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=56114@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
/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).