From: ng0 <contact.ng0@cryptolab.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-pyodbc-c.
Date: Thu, 26 Jan 2017 16:55:11 +0000 [thread overview]
Message-ID: <87mvedkbgw.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170126002621.9247-1-dannym@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> writes:
> * gnu/packages/databases.scm (python-pyodbc-c, python2-pyodbc-c):
> New variables.
> ---
> gnu/packages/databases.scm | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/gnu/packages/databases.scm b/gnu/packages/databases.scm
> index e8be17980..fc576888d 100644
> --- a/gnu/packages/databases.scm
> +++ b/gnu/packages/databases.scm
> @@ -1312,3 +1312,29 @@ development.")
> ;; test/crypto.test are licensed under a 3-clause BSD license. All other
> ;; source files are in the public domain.
> (license (list license:public-domain license:bsd-3))))
> +
> +(define-public python-pyodbc-c
> + (package
> + (name "python-pyodbc-c")
> + (version "3.1.2")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (string-append "https://gitlab.com/daym/pyodbc-c/repository/"
> + "archive.tar.gz?ref=v" version))
> + (sha256
> + (base32 "0nl11n3mgrcfnhimjqgv48rxqnb21l5m6s7p8ps2fa4nn4z6rzy0"))
I would put this as
(sha256
(base32
""))
but I guess this works too as long as lint is happy.
> + (file-name (string-append name "-" version ".tar.gz"))))
> + (build-system python-build-system)
> + (inputs
> + `(("unixodbc" ,unixodbc)))
> + (arguments
> + `(#:tests? #f ; no tests exist
> + ))
> + (home-page "https://github.com/mkleehammer/pyodbc")
This is pulled from gitlab and the homepage is on gitlab? I think
it's better to use the gitlab repository as home-page then, or
what's the reason?
> + (synopsis "Python ODBC Library")
> + (description "This package provides a Python DB-API driver for ODBC.")
If I remember correctly, we should avoid starting synopsis and
description with words like "This". What about:
(description "@code{python-pyodbc-c} provides …"
> + (license (license:x11-style "file://LICENSE.TXT"))))
> +
> +(define-public python2-pyodbc-c
> + (package-with-python2 python-pyodbc-c))
>
Besides those small comments it looks good to me!
--
♥Ⓐ ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-01-26 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 0:26 [PATCH] gnu: Add python-pyodbc-c Danny Milosavljevic
2017-01-26 16:55 ` ng0 [this message]
2017-01-26 18:14 ` Marius Bakke
2017-01-26 18:21 ` Danny Milosavljevic
2017-01-26 18:33 ` Marius Bakke
2017-01-26 18:27 ` [PATCH v2] " Danny Milosavljevic
2017-02-07 18:36 ` Kei Kebreau
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=87mvedkbgw.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=contact.ng0@cryptolab.net \
--cc=dannym@scratchpost.org \
--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).