unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Sarah Morgensen <iskarian@mgsn.dev>,
	50349@debbugs.gnu.org, guix-patches@gnu.org
Subject: bug#50349: [PATCH] packages: Add 'define-package' syntax.
Date: Sat, 04 Sep 2021 12:09:26 +0200	[thread overview]
Message-ID: <87y28caazy.fsf@nckx> (raw)
In-Reply-To: <757b7543b931335c3725264edfbc79c012aa10fc.camel@telenet.be>

[-- Attachment #1: Type: text/plain, Size: 617 bytes --]

All,

To keep a link with previous ‘define-package’ discussion, I've 
merged this bug with #15284.  It was never resolved IMO and things 
have changed since 2013 with the label-less input style.

Maxime Devos 写道:
> This could be even shorter in the special case that the variable 
> name
> and package name are the same (modulo types):
>
> (define-package "my-favorite-package"
>   (version ...)
>   ...)

(define-anything STRING ...) is just too weird to ack.  Are there 
any package names that aren't currently valid symbols?  Is there a 
good reason for them?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

       reply	other threads:[~2021-09-04 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15d01b32313f5f2f291b120597719ae92bd26acd.1630639896.git.iskarian@mgsn.dev>
     [not found] ` <757b7543b931335c3725264edfbc79c012aa10fc.camel@telenet.be>
2021-09-04 10:09   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-09-04 14:29     ` bug#50349: [PATCH] packages: Add 'define-package' syntax Taylan Kammer
2021-09-04 14:44       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-09-04 17:23         ` Taylan Kammer
2021-09-04 18:53           ` Sarah Morgensen
2021-09-04 21:01             ` Taylan Kammer
2021-09-04 23:17   ` Sarah Morgensen

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=87y28caazy.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 \
    /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).