From: Andreas Enge <andreas@enge.fr>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-contextlib2
Date: Wed, 18 Nov 2015 09:46:40 +0100 [thread overview]
Message-ID: <20151118084640.GA4950@debian.ntu.edu.sg> (raw)
In-Reply-To: <CAEKzfHki1Nq01yUrDf08gFfc+dxahS2kBcoqwhn_1zWWt8Lq8w@mail.gmail.com>
Hello,
and congratulations for your first package!
Upon a quick glance, I have the following comments:
> gnu: Add python-contextlib2
Please add a "." at the end of the line.
> * gnu/packages/python.scm (python-contextlib2, python2-contextlib2):
> New variables.
> gnu/packages/patches/python-contextlib2.patch | 51 +++++++++++++++++++++++++++
> gnu/packages/python.scm | 24 +++++++++++++
> 2 files changed, 75 insertions(+)
You also need to add the patch to gnu-system.am. Then add two lines to the
commit log explaining the changes to the two other files; you will find
examples in the commit history.
At the top of a patch file, we usually provide a little explanation of why
the patch is needed; if it concerns a problem to be fixed upstream, we
usually report the bug and add a reference to the bug url; if it comes
from another distribution we give the reference.
Did you run "./pre-inst-env guix lint python-contextlib2" etc.? This can
detect potential problems. (I did not try it on your patch, and am just
asking because I tend to forget it myself.)
I let the python gurus comment on the content of the package.
Andreas
next prev parent reply other threads:[~2015-11-18 8:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 8:31 [PATCH] gnu: Add python-contextlib2 Chris Marusich
2015-11-18 8:46 ` Andreas Enge [this message]
2015-11-18 8:46 ` Chris Marusich
2015-11-18 12:55 ` Ben Woodcroft
2015-11-21 21:28 ` Chris Marusich
2015-11-26 13:44 ` Ludovic Courtès
2015-12-01 8:22 ` Chris Marusich
2015-12-06 21:49 ` Ludovic Courtès
2015-12-08 5:14 ` Chris Marusich
2015-12-13 23:16 ` Ludovic Courtès
2015-12-14 2:15 ` Chris Marusich
2015-12-14 8:44 ` 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=20151118084640.GA4950@debian.ntu.edu.sg \
--to=andreas@enge.fr \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@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).