From: Marius Bakke <mbakke@fastmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>, 29144@debbugs.gnu.org
Subject: [bug#29144] [PATCH 1/3] gnu: Add pydot.
Date: Sun, 05 Nov 2017 17:27:12 +0100 [thread overview]
Message-ID: <87vaiog07z.fsf@fastmail.com> (raw)
In-Reply-To: <20171104193643.1387-1-boskovits@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
Gábor Boskovits <boskovits@gmail.com> writes:
> * gnu/packages/python.scm (python-pydot): New variable.
Thanks! I think we can add this package to graphviz.scm instead, since
python.scm is very generic (and huge!). A few comments..
> +(define-public python-pydot
> + (package
> + (name "python-pydot")
> + (version "1.2.3")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (pypi-uri "pydot" version))
> + (sha256
> + (base32
> + "00imlz0033dygb9gdag1xr0cybn33gk5jsdi9ffbszzr97rd7dgd"))))
> + (build-system python-build-system)
> + (inputs
> + `(("python-pyparsing",python-pyparsing)
> + ("python-chardet",python-chardet)))
According to setup.py, chardet is only needed for tests, so it should be
a "native-input. Pyparsing OTOH should be a propagated-input since it
is required at runtime.
I haven't tried building it since it does not apply on current 'master'
after 2e15906c1c1337945b6578c7f58a4fd4af52aaf3. Can you send an updated
patch please, for 'graphviz.scm'? Please also try to get the unit tests
running if they are not already, see the '.travis.yml' file for how
upstream does it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-11-05 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 19:36 [bug#29144] [PATCH 1/3] gnu: Add pydot Gábor Boskovits
2017-11-05 16:27 ` Marius Bakke [this message]
2017-11-06 8:30 ` [bug#29144] [PATCH] gnu: add pydot Gábor Boskovits
2017-11-06 8:32 ` [bug#29144] Updated patch Gábor Boskovits
2017-11-07 20:07 ` bug#29144: " Marius Bakke
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=87vaiog07z.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=29144@debbugs.gnu.org \
--cc=boskovits@gmail.com \
/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).