unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Cyril Roelandt <tipecaml@gmail.com>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add pyparsing.
Date: Wed, 26 Nov 2014 17:40:07 +0100	[thread overview]
Message-ID: <54760267.8070203@gmail.com> (raw)
In-Reply-To: <CAKrPhPOEKgnUKgq8xgjiefFaASDZBM+k8SfqhbQFt1eo3Zd=hQ@mail.gmail.com>

On 11/25/2014 06:51 PM, Federico Beffa wrote:
> Cyril Roelandt <tipecaml@gmail.com> writes:
> 
>>
>> Maybe you could add the PyPI mirror here.
>>
> 
> I'm not sure I understand. Do you mean replace or really add? A second
> uri field? Could you give an example? The sourceforge download site is
> the one mentioned on the homepage.

Yes. The "uri" field can be a list (see libpng for instance). It would
be nice to have two reliable mirrors here.

> 
>>
>> There is a "unitTests.py" that can be run manually, if I'm not mistaken.
>> Maybe you could replace the check phase ?
>>
> 
> I do not think so.  I do not see any reference to tests in the README
> and other source files and I can't find a file called "unitTests.py".

Oh, that might just be in the SVN repository, then.

> 
>>
>> I trust you on the doc thing :) Is it something that could somehow be
>> part of the python build system?
>>
> 
> I'm not a python expert :-) From the few packages that I prepared
> lately, I have the impression that each python library does something
> different with the documentation.

Sad but true.

> 
>>
>> Do not start the synopsis by "a". You may want to run "guix lint" on
>> your package to find such issues.
>>
> 
> Ooops, forgot to run that.
> 
> Thanks for the review,

Thanks for the package!

Cyril.

  reply	other threads:[~2014-11-26 16:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 16:55 [PATCH] gnu: Add pyparsing Federico Beffa
2014-11-25 17:11 ` Ludovic Courtès
2014-11-25 17:17 ` Cyril Roelandt
2014-11-25 17:21 ` Eric Bavier
2014-11-25 17:51   ` Federico Beffa
2014-11-26 16:40     ` Cyril Roelandt [this message]
2014-11-25 19:47   ` Federico Beffa

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=54760267.8070203@gmail.com \
    --to=tipecaml@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).