unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Joshua Branson <jbranso@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Should 'build-expression->derivation' be used for new build systems?
Date: Sat, 20 Oct 2018 12:03:55 +0200	[thread overview]
Message-ID: <87tvlhaq9g.fsf@gnu.org> (raw)
In-Reply-To: <87zhv9rk5o.fsf@fastmail.com> (Joshua Branson's message of "Fri, 19 Oct 2018 12:11:31 -0400")

Hello,

Joshua Branson <jbranso@fastmail.com> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:

[...]

>> The story of ‘build-expression->derivation’ is that of an unfinished
>> transition to G-expressions.  :-)
>>
>> There’s a branch called ‘wip-build-systems-gexp’ that aims to complete
>> that transition, but I haven’t yet gotten around to actually finishing
>> the work.  This is one of the things I want us to complete for 1.0
>> though, so sooner rather than later.
>
> May I ask why the transition?  Just curious.

G-expressions address shortcomings of plain s-expressions when used to
write build expressions as in Guix and for code generation in general
(“code staging”); see:

  https://www.gnu.org/software/guix/manual/en/html_node/G_002dExpressions.html
  https://hal.inria.fr/hal-01580582/en

Ludo’.

      reply	other threads:[~2018-10-20 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 19:29 Should 'build-expression->derivation' be used for new build systems? Alex Vong
2018-10-19 14:05 ` Ludovic Courtès
2018-10-19 16:11   ` Joshua Branson
2018-10-20 10:03     ` Ludovic Courtès [this message]

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=87tvlhaq9g.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jbranso@fastmail.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 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).