From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pyside-tools: remove package
Date: Tue, 30 Jul 2019 23:10:47 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13423@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
There is a new pull request by knusbaum against master on the void-packages repository
https://github.com/knusbaum/void-packages REMOVE_PYSIDE-TOOLS
https://github.com/void-linux/void-packages/pull/13423
pyside-tools: remove package
Resolves #12844
pyside-tools was broken when python-pyside was removed here: https://github.com/void-linux/void-packages/pull/11064
It looks like we do not intend to support these bindings, so removing this package is the correct solution.
A patch file from https://github.com/void-linux/void-packages/pull/13423.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-REMOVE_PYSIDE-TOOLS-13423.patch --]
[-- Type: text/x-diff, Size: 1782 bytes --]
From 06c8aeb9746ba318584b8eeb9ca5490bbff65445 Mon Sep 17 00:00:00 2001
From: Kyle Nusbaum <kylenusbaum@granular.ag>
Date: Tue, 30 Jul 2019 16:05:19 -0500
Subject: [PATCH] pyside-tools: remove package
---
srcpkgs/pyside-tools/INSTALL.msg | 1 +
srcpkgs/pyside-tools/template | 19 +++++--------------
2 files changed, 6 insertions(+), 14 deletions(-)
create mode 100644 srcpkgs/pyside-tools/INSTALL.msg
diff --git a/srcpkgs/pyside-tools/INSTALL.msg b/srcpkgs/pyside-tools/INSTALL.msg
new file mode 100644
index 00000000000..fdb45eb0f42
--- /dev/null
+++ b/srcpkgs/pyside-tools/INSTALL.msg
@@ -0,0 +1 @@
+pyside-tools is no longer provided by Void Linux, and will be fully removed from the repos on 2019-10-30
diff --git a/srcpkgs/pyside-tools/template b/srcpkgs/pyside-tools/template
index d5dee735df1..27cfc18eea4 100644
--- a/srcpkgs/pyside-tools/template
+++ b/srcpkgs/pyside-tools/template
@@ -1,18 +1,9 @@
# Template file for 'pyside-tools'
pkgname=pyside-tools
version=0.2.15
-revision=1
-wrksrc="Tools-${version}"
-build_style=cmake
-
-# libshiboken-python-devel libpyside-python-devel has distinct conventions
-configure_args="-DPYTHON_SUFFIX=-python2.7 -DPYTHON_BASENAME=-python2.7"
-makedepends="libshiboken-python-devel libpyside-python-devel qt-devel"
-depends="python"
-pycompile_module="pysideuic"
-short_desc="LGPL-licensed Python2 bindings for the Qt4 toolkit"
-maintainer="yopito <pierre.bourgin@free.fr>"
-license="LGPL-2.1"
+revision=2
+archs=noarch
+build_style=meta
+short_desc="LGPL-licensed Python2 bindings for the Qt4 toolkit (removed package)"
+license="BSD-2-Clause"
homepage="https://wiki.qt.io/"
-distfiles="https://github.com/PySide/Tools/archive/${version}.tar.gz"
-checksum=8a7fe786b19c5b2b4380aff0a9590b3129fad4a0f6f3df1f39593d79b01a9f74
next reply other threads:[~2019-07-30 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 21:10 voidlinux-github [this message]
2019-07-30 21:29 ` [PR PATCH] [Merged]: " voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13423@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).