From: ludo@gnu.org (Ludovic Courtès)
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Agreeing on some "rules" for packaging.
Date: Wed, 28 Aug 2013 22:57:45 +0200 [thread overview]
Message-ID: <87fvtt8ree.fsf@gnu.org> (raw)
In-Reply-To: <521E423C.7010107@gmail.com> (Cyril Roelandt's message of "Wed, 28 Aug 2013 20:32:28 +0200")
Cyril Roelandt <tipecaml@gmail.com> skribis:
> On 08/28/2013 02:51 PM, Ludovic Courtès wrote:
>> Cyril Roelandt <tipecaml@gmail.com> skribis:
[...]
>>> I would also like to define a standard way to order the "#:use-module"
>>> at the beginning of each file, and agree on other "cosmetic" rules.
>>
>> Not convinced about the ordering. ;-)
>>
>
> Isn't there such a convention in Scheme ?
Not that I know of.
I generally put the (guix ...) modules first, and the (gnu ...) second,
I think. IOW, the “foundational” first.
>> These are good examples of the kind of rules we may want to discuss and
>> adopt.
>
>
> I'm also wondering how to name python packages. foo ? python-foo and
> python3-foo ? python2-foo and python-foo ?
Presumably pythonX-foo. Andreas?
Ludo’.
next prev parent reply other threads:[~2013-08-28 21:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 21:46 Agreeing on some "rules" for packaging Cyril Roelandt
2013-08-27 22:31 ` Nikita Karetnikov
2013-08-28 6:29 ` Andreas Enge
2013-08-28 12:51 ` Ludovic Courtès
2013-08-28 18:32 ` Cyril Roelandt
2013-08-28 20:56 ` Andreas Enge
2013-08-28 22:42 ` Ludovic Courtès
2013-08-28 22:37 ` Cyril Roelandt
2013-08-29 8:59 ` Ludovic Courtès
2013-08-30 21:59 ` Andreas Enge
2013-08-31 9:31 ` Ludovic Courtès
2013-08-31 10:00 ` Andreas Enge
2013-08-31 10:22 ` Ludovic Courtès
2013-08-28 20:57 ` Ludovic Courtès [this message]
2013-08-30 18:15 ` Nikita Karetnikov
2013-08-30 19:35 ` Ludovic Courtès
2013-08-30 21:09 ` Nikita Karetnikov
2013-08-30 21:22 ` Ludovic Courtès
2013-08-30 21:49 ` Ludovic Courtès
2013-09-07 8:20 ` Nikita Karetnikov
2013-09-07 8:36 ` Andreas Enge
2013-09-07 13:11 ` 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=87fvtt8ree.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=tipecaml@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).