From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Taylan Kammer <taylan.kammer@gmail.com>
Cc: 50349@debbugs.gnu.org, Sarah Morgensen <iskarian@mgsn.dev>,
Maxime Devos <maximedevos@telenet.be>,
guix-patches@gnu.org
Subject: bug#50349: [PATCH] packages: Add 'define-package' syntax.
Date: Sat, 04 Sep 2021 16:44:49 +0200 [thread overview]
Message-ID: <87bl58wfk7.fsf@nckx> (raw)
In-Reply-To: <95c92fc5-1fcf-b347-370e-d1943f22c2c3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Taylan Kammer 写道：
> To me the most obvious thing to do seems
>
> (define-package foo ...) ;no explicit name needed
>
> to bind the variable 'foo' and use symbol->string for the name
> of the
> package, with the possibility to override the name like
>
> (define-package foo (name "foobar") ...)
>
> which would bind the variable 'foo' to a package named "foobar".
Right, that's what I meant, and it's how I read bug #15284, and it
looks remarkably like the form I use in my personal channels (and
I'm sure I'm not the first! :-).
You're much better at the language/implementation side of things
than I am, Taylan. Would this negatively affect performance
(including ‘guix pull’ compilation)?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-09-04 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 4:06 [bug#50349] [PATCH] packages: Add 'define-package' syntax Sarah Morgensen
2021-09-03 5:41 ` zimoun
2021-09-03 21:56 ` Sarah Morgensen
2021-09-04 8:42 ` Maxime Devos
2021-09-04 10:09 ` bug#50349: " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-09-04 14:29 ` Taylan Kammer
2021-09-04 14:44 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-09-04 17:23 ` Taylan Kammer
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=87bl58wfk7.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=50349@debbugs.gnu.org \
--cc=guix-patches@gnu.org \
--cc=iskarian@mgsn.dev \
--cc=maximedevos@telenet.be \
--cc=me@tobias.gr \
--cc=taylan.kammer@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).