all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 14:51:29 +0200	[thread overview]
Message-ID: <87sixuc71q.fsf@gnu.org> (raw)
In-Reply-To: <521D1E38.9090604@gmail.com> (Cyril Roelandt's message of "Tue, 27 Aug 2013 23:46:32 +0200")

Cyril Roelandt <tipecaml@gmail.com> skribis:

> At the GHM, a Fedora hacker (whose name I forgot) suggested that it
> might be time for us to write down some "rules" as to how packaging
> should be done.

Sounds like a good idea.  In general, when working in a group, I think
it’s better to discuss what our expectations are, and write as much of
it down, to avoid any misunderstandings or frustration.  So yes, let’s
do it.

> For instance, Andreas suggested that patches should only be used if we
> think they might be applied upstream, thus keeping the patches/
> directory as small as possible;

Agreed.  Also, patches should start with a comment saying what they do,
and possibly what their upstream status is (submitted, will never be
submitted because it’s Guix-specific, etc.); perhaps the format of that
comment could even be formalized.

> modifications specific to Guix should be written in Scheme.

Sometimes that may be hard or inconvenient though, so I would not set
that in stone.

> 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.  ;-)

> What do you think ?

These are good examples of the kind of rules we may want to discuss and
adopt.

What about discussing them as patches for the “Packaging Guidelines”
section of the manual, for example?  (With one thread per suggestion.)

Thanks!

Ludo’.

  parent reply	other threads:[~2013-08-28 12:52 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sixuc71q.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.