From: Bruno Victal <mirai@makinata.eu>
To: Thomas Albers Raviola <thomas@thomaslabs.org>
Cc: 50578@debbugs.gnu.org
Subject: [bug#50578] [PATCH] gnu: Add minipro
Date: Mon, 3 Apr 2023 12:17:10 +0100 [thread overview]
Message-ID: <7a7a5e68-860d-a1f0-3a66-9ac6d5afeda3@makinata.eu> (raw)
In-Reply-To: <87ilee6ifz.fsf@alpha.mail-host-address-is-not-set>
On 2023-04-02 23:13, Thomas Albers Raviola via Guix-patches via wrote:
>
> I fail to see the purpose of G-Expressions over normal backticks for the
> build phases as no file-like or package is being used inside of them. I
> am missing something?
They allow for a separation between host and build code.
There's a post at <https://guix.gnu.org/blog/2021/the-big-change/> and
a chapter in the manual which explains them in further detail.
One bonus point is that for outputs, instead of writing:
--8<---------------cut here---------------start------------->8---
#~(let ((out (assoc-ref %outputs "out")))
(list (string-append "VERSION=" #$version)
(string-append "PREFIX=" out)
--8<---------------cut here---------------end--------------->8---
you can directly write this without the assoc-ref machinery:
--8<---------------cut here---------------start------------->8---
#~(list (string-append "VERSION=" #$version)
(string-append "PREFIX=" #$output)
--8<---------------cut here---------------end--------------->8---
HTH!
Cheers,
Bruno
next prev parent reply other threads:[~2023-04-03 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 10:56 [bug#50578] [PATCH] gnu: Add minipro Thomas Albers via Guix-patches via
2023-03-31 11:09 ` Bruno Victal
2023-04-01 15:41 ` Thomas Albers Raviola via Guix-patches via
2023-04-01 17:46 ` Bruno Victal
2023-04-02 22:13 ` Thomas Albers Raviola via Guix-patches via
2023-04-03 11:17 ` Bruno Victal [this message]
2023-04-03 13:20 ` Thomas Albers Raviola via Guix-patches via
2023-04-02 22:08 ` Thomas Albers via Guix-patches via
2023-04-03 13:17 ` Thomas Albers via Guix-patches via
2023-04-22 12:48 ` Bruno Victal
2023-04-23 15:24 ` bug#50578: " 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=7a7a5e68-860d-a1f0-3a66-9ac6d5afeda3@makinata.eu \
--to=mirai@makinata.eu \
--cc=50578@debbugs.gnu.org \
--cc=thomas@thomaslabs.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).