From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Some macros to make package definitions prettier
Date: Wed, 04 Mar 2015 10:52:54 +0100 [thread overview]
Message-ID: <87lhjdks21.fsf@gnu.org> (raw)
In-Reply-To: <87oao9em0y.fsf@taylan.uni.cx> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Tue, 03 Mar 2015 23:47:25 +0100")
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> I actually agree. Well, next round?
>
> If you want. :-) I thought it might be too much to have a second commit
> that touches all recipes where 'modify-phases' is used, but maybe I'm
> being too pedantic.
Currently ‘modify-phases’ is only used in build systems, so it’s not too
late.
>> In think Guile 2.1 is standards-compliant in that respect though. A
>> related problem will be the ‘_’ procedure of (guix ui) that will need
>> to be renamed (which is annoying at worst, but OK.) ‘delete’ might be
>> more of a problem.
>
> Hm, if Guile 2.1 intends to have a fully hygienic syntax-rules by
> default, I would expect it to offer a way to enable the alternative
> behavior for a given syntax-rules usage, because AFAIK it's quite common
> (if not more common) that unhygienic matching is desired.
Yeah I have mixed feelings about it.
> Otherwise, we could just use slightly different identifiers:
> phase-delete, phase-replace, phase-add-before, phase-add-after.
This is an example of an undesirable side effect. :-)
Ludo’.
next prev parent reply other threads:[~2015-03-04 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 16:42 Some macros to make package definitions prettier Taylan Ulrich Bayırlı/Kammer
2015-02-25 17:04 ` Thompson, David
2015-02-25 17:06 ` Thompson, David
2015-02-25 19:27 ` Taylan Ulrich Bayırlı/Kammer
2015-02-25 20:54 ` Taylan Ulrich Bayırlı/Kammer
2015-02-25 18:12 ` Andreas Enge
2015-02-25 19:46 ` Taylan Ulrich Bayırlı/Kammer
2015-02-25 20:24 ` Thompson, David
2015-02-25 23:32 ` Ludovic Courtès
2015-02-26 11:07 ` Taylan Ulrich Bayırlı/Kammer
2015-02-26 21:39 ` Ludovic Courtès
2015-03-03 16:49 ` Taylan Ulrich Bayırlı/Kammer
2015-03-03 20:44 ` Ludovic Courtès
2015-03-03 22:47 ` Taylan Ulrich Bayırlı/Kammer
2015-03-04 9:52 ` Ludovic Courtès [this message]
2015-02-26 21:41 ` 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=87lhjdks21.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@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 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).