From: yoctocell <yoctocell@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-matplotlib: update to 3.3.0
Date: Fri, 17 Jul 2020 21:20:07 +0200 [thread overview]
Message-ID: <20200717192007.TgaSj80oT-Lnl8R32rKvoUOSsO7GZ-AEeNGvSMtntEA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23613@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
There is an updated pull request by yoctocell against master on the void-packages repository
https://github.com/yoctocell/void-packages matplotlib-3.3.0
https://github.com/void-linux/void-packages/pull/23613
python3-matplotlib: update to 3.3.0
None
A patch file from https://github.com/void-linux/void-packages/pull/23613.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-matplotlib-3.3.0-23613.patch --]
[-- Type: text/x-diff, Size: 1767 bytes --]
From a1d894864acb3a26ff07245ba7b445b4c12b8517 Mon Sep 17 00:00:00 2001
From: yoctocell <attocell.name@protonmail.com>
Date: Fri, 17 Jul 2020 16:01:06 +0200
Subject: [PATCH] python3-matplotlib: update to 3.3.0
---
srcpkgs/python3-matplotlib/template | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-matplotlib/template b/srcpkgs/python3-matplotlib/template
index 7182291fa36..7432eb0591c 100644
--- a/srcpkgs/python3-matplotlib/template
+++ b/srcpkgs/python3-matplotlib/template
@@ -1,12 +1,13 @@
# Template file for 'python3-matplotlib'
pkgname=python3-matplotlib
-version=3.2.1
+version=3.3.0
revision=1
wrksrc="matplotlib-${version}"
build_style=python3-module
-hostmakedepends="pkg-config python3-setuptools python3-numpy"
+build_helper="numpy"
+hostmakedepends="pkg-config python3-setuptools"
# XXX use internal copy of agg, highly patched
-makedepends="python3-devel freetype-devel libpng-devel"
+makedepends="python3-devel freetype-devel libpng-devel libqhull-devel"
depends="python3-matplotlib-data>=${version}_${revision} python3-numpy
python3-dateutil python3-parsing python3-cycler python3-kiwisolver"
short_desc="Python3 2D/3D plotting library"
@@ -14,7 +15,15 @@ maintainer="Alessio Sergi <al3hex@gmail.com>"
license="custom:matplotlib, BSD-3-Clause, MIT"
homepage="https://matplotlib.org/"
distfiles="https://github.com/matplotlib/matplotlib/archive/v${version}.tar.gz"
-checksum=5462728ed3be60af21bd8a6b33f5f1632dabdb3c1b3cc279cffb05926a48255c
+checksum=ee72a23bd5310a69a96c8527901d4ce71820bcbee260c04d1ef2069201c9b98a
+
+pre_build() {
+ cat <<-EOF > setup.cfg
+ [libs]
+ system_freetype = true
+ system_qhull = true
+ EOF
+}
post_install() {
vdoc "${FILESDIR}/README.voidlinux"
next prev parent reply other threads:[~2020-07-17 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 14:02 [PR PATCH] " yoctocell
2020-07-17 18:15 ` [PR PATCH] [Updated] " yoctocell
2020-07-17 18:56 ` [PR REVIEW] " ahesford
2020-07-17 18:56 ` ahesford
2020-07-17 19:20 ` yoctocell [this message]
2020-07-17 19:37 ` [PR PATCH] [Merged]: " ahesford
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=20200717192007.TgaSj80oT-Lnl8R32rKvoUOSsO7GZ-AEeNGvSMtntEA@z \
--to=yoctocell@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).