From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel@gnu.org
Subject: Re: [PATCH 1/4] gnu: Add python-avro.
Date: Mon, 26 Sep 2016 11:31:48 +0200 [thread overview]
Message-ID: <57E8EB04.2040905@crazy-compilers.com> (raw)
In-Reply-To: <20160925211728.7636-1-mbakke@fastmail.com>
Am 25.09.2016 um 23:17 schrieb Marius Bakke:
> +;;; Avro uses a single source repository for all implementations. The individual
> +;;; released versions often have missing or incomplete test data, so we define
> +;;; the common source here for use in all avro packages.
> +(define (avro-version) "1.8.1")
> +(define (avro-source version)
With "Avro uses a single source repository for all implementations " you
mean for both Python 2 and Python 3? Well, this is the common case :-)
Any other packages do have this and we never use a separate definition
for source or version. Please have a look at e.g. python-graphql-relay
(picked as example at random).
> + `(#:tests? #f ; Requires Apache Ivy.
Please add, why this is a problem. If Ivy is not yet pacakges, I suggest
adding something like "TODO: enable if Apache Ivy is packaged".
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2016-09-26 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 21:17 [PATCH 1/4] gnu: Add python-avro Marius Bakke
2016-09-25 21:17 ` [PATCH 2/4] gnu: Add python-sphinx-bootstrap-theme Marius Bakke
2016-09-26 9:35 ` Hartmut Goebel
2016-09-25 21:17 ` [PATCH 3/4] gnu: Add python-sphinx-argparse Marius Bakke
2016-09-26 9:36 ` Hartmut Goebel
2016-09-25 21:17 ` [PATCH 4/4] gnu: Add python2-pbcommand Marius Bakke
2016-09-26 9:38 ` Hartmut Goebel
2016-09-26 9:31 ` Hartmut Goebel [this message]
2016-09-26 19:56 ` [PATCH 1/4] gnu: Add python-avro Marius Bakke
2016-10-04 9:35 ` Ludovic Courtès
2016-10-04 9:32 ` 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=57E8EB04.2040905@crazy-compilers.com \
--to=h.goebel@crazy-compilers.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 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.