unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Naming scheme for Python packages
Date: Wed, 4 Sep 2013 23:08:36 +0200	[thread overview]
Message-ID: <20130904210836.GB8425@debian> (raw)
In-Reply-To: <87li3c8g56.fsf@gnu.org>

On Wed, Sep 04, 2013 at 10:51:17PM +0200, Ludovic Courtès wrote:
> However, I don’t think that scheme should be followed for variable
> names: it’s tedious to type, and Guile offers mechanisms to
> select/rename bindings imported from other bindings.
> Thus I would do:
>   (define pytz
>     (package
>       (name "python-pytz")
>       ...))

Well, we also have the policy so far that variable name = name field.
I find it consistent, and do not mind typing a few "python-" more or less.
It is not what makes packaging quite a bit of work...

But if others agree, this can still be changed quite easily.

You may wish to suggest a patch to the "packaging guidelines" in the documen-
tation; the ease or lack of ease to formulate a coherent guideline could be
an indication on what we should do...

Andreas

  parent reply	other threads:[~2013-09-04 21:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1VHJTB-0006ys-7X@vcs.savannah.gnu.org>
2013-09-04 20:51 ` Naming scheme for Python packages Ludovic Courtès
2013-09-04 20:52   ` Cyril Roelandt
2013-09-04 21:16     ` Andreas Enge
2013-09-04 21:07   ` Cyril Roelandt
2013-09-04 21:36     ` Andreas Enge
2013-09-04 21:08   ` Andreas Enge [this message]
2013-09-04 21:32     ` Andreas Enge
2013-09-05 13:00       ` Ludovic Courtès
2013-09-06 21:53         ` Andreas Enge
2013-09-07 12:49           ` Ludovic Courtès
2013-09-07 21:25             ` Andreas Enge
2013-09-08 14:03               ` Ludovic Courtès
2013-09-08 14:51                 ` Andreas Enge
2013-09-08 20:00                   ` 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=20130904210836.GB8425@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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).