From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>, 29850@debbugs.gnu.org
Subject: [bug#29850] [PATCH v3] gnu: Add python-hidapi.
Date: Wed, 27 Dec 2017 22:58:03 +0100 [thread overview]
Message-ID: <87tvwbdeac.fsf@fastmail.com> (raw)
In-Reply-To: <20171227195351.10879-1-dannym@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 3512 bytes --]
Hello!
Danny Milosavljevic <dannym@scratchpost.org> writes:
> * gnu/packages/libusb.scm (python-hidapi, python2-hidapi): New variables.
[...]
> +(define-public python-hidapi
> + (package
> + (name "python-hidapi")
> + (version "0.7.99.post21")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (pypi-uri "hidapi" version))
> + (sha256
> + (base32
> + "15ws59zdrxahf3k7z5rcrwc4jgv1307anif8ixm2cyb9ask1mgp0"))
Please re-indent the entire expression with emacs or ./etc/indent-code.el.
> + (modules '((guix build utils)))
> + (snippet
> + ;; Remove bundled libraries.
> + '(begin
> + (delete-file-recursively "hidapi")))))
In absense of a consensus on unspecified return values, return #t here.
> + (build-system python-build-system)
> + (arguments
> + `(#:phases
> + (modify-phases %standard-phases
> + (add-after 'unpack 'patch-configuration
> + (lambda* (#:key inputs #:allow-other-keys)
> + (substitute* "setup.py"
> + (("'/usr/include/libusb-1.0'")
> + (string-append "'" (assoc-ref inputs "libusb")
> + "/include/libusb-1.0'"))
> + (("'/usr/include/hidapi'")
> + (string-append "'" (assoc-ref inputs "hidapi")
> + "/include/hidapi'")))
> + #t))
> + (replace 'build
> + (lambda _
> + ;; Necessary because python-build-system drops the arguments.
> + (invoke "python" "setup.py" "build" "--with-system-hidapi")))
> + (replace 'check
> + (lambda _
> + ;; Necessary because python-build-system drops the arguments.
> + (invoke "python" "setup.py" "test" "--with-system-hidapi")))
> + (replace 'install
> + (lambda* (#:key outputs #:allow-other-keys)
> + ;; Necessary because python-build-system drops the arguments.
> + (invoke "python" "setup.py" "install" "--with-system-hidapi"
> + (string-append "--prefix=" (assoc-ref outputs "out"))
> + "--single-version-externally-managed" "--root=/"))))))
I don't think repeating the same comment thrice is necessary. Maybe
just add an XXX note at the top mentioning why we do this dance rather
than use python-build-system directly.
It would be good to extend python-build-system to support this however.
#:setuppy-flags? :)
> + (inputs
> + `(("hidapi" ,hidapi)
> + ("libusb" ,libusb)
> + ("eudev" ,eudev)))
> + (native-inputs
> + `(("python-cython" ,python-cython)))
> + (home-page "https://github.com/trezor/cython-hidapi")
> + (synopsis "Cython interface to hidapi")
> + (description "This package provides a Cython interface to @code{hidapi}.")
> + ;; The library can be used under either of these licenses.
> + ;; TODO Add cython-hidapi DIY license?
I think this TODO can be removed, we have lots of "one-off" licenses
scattered throughout.
> + (license (list gpl3 bsd-3
> + (non-copyleft
> + "https://github.com/trezor/cython-hidapi/blob/master/LICENSE-orig.txt")))))
The (non-copyleft ...) procedure takes an optional comment. This
license is short enough to fit, maybe we can just add the "whole" text?
No strong opinion. The rest LGTM!
> +
> +(define-public python2-hidapi
> + (package-with-python2 python-hidapi))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-12-27 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 23:03 [bug#29850] [PATCH] gnu: Add python-hidapi Danny Milosavljevic
2017-12-26 18:44 ` Leo Famulari
2017-12-27 0:23 ` Danny Milosavljevic
2017-12-27 19:20 ` Leo Famulari
2017-12-27 11:27 ` [bug#29850] [PATCH v2] " Danny Milosavljevic
2017-12-27 19:53 ` [bug#29850] [PATCH v3] " Danny Milosavljevic
2017-12-27 21:58 ` Marius Bakke [this message]
2017-12-28 7:41 ` bug#29850: " Danny Milosavljevic
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=87tvwbdeac.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=29850@debbugs.gnu.org \
--cc=dannym@scratchpost.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).