Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43041 - [python-pyside] missing dev tools

Attached to Project: Community Packages
Opened by kachelaqa (kachelaqa) - Sunday, 07 December 2014, 21:59 GMT
Last edited by Florian Pritz (bluewind) - Monday, 29 December 2014, 20:43 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The dev tools (pyside-lupdate, pyside-rcc, pyside-uic) need to be added to the pyside packages. Or possibly there should be a separate pyside-tools package to contain them.

Additional info:

Affects version 1.2.2-3 for both Python2 and Python3
This task depends upon

Closed by  Florian Pritz (bluewind)
Monday, 29 December 2014, 20:43 GMT
Reason for closing:  Implemented
Comment by Florian Pritz (bluewind) - Monday, 08 December 2014, 12:31 GMT
Those tools are shipped in a separate tarball and should therefore go into their own package. I pulled in python-pyside because it's a dependency of freecad, but I'm not interested in pyside besides that, sorry.

The python-pyside-tools PKGBUILD in AUR looks rather hacky (symlinking a /usr/lib/python3 file into the python2 dir), it doesn't build split packages for both python versions (which would get rid of the optdeps) and uses sed to create pyside-uic-py2. I'm also not a fan of the calls to python to figure out the version strings, but I have no idea if there are cleaner alternatives so those might be okay. If someone were to clean that up (mainly the splitting and the symlink, as for the rest I know too little about the package) I might take another look.

You might want to look at the python-pyside and shiboken PKGBUILDs in our repo for inspiration. Also shiboken builds the same executables for both python versions, I don't know if that's the case for pyside-tools.
Comment by kachelaqa (kachelaqa) - Monday, 08 December 2014, 17:00 GMT
First of all: thanks for getting the main pyside packages into community. I had been planning to create a full set of packages for my local repository, but so far I've got only the ones for python2.

I will have a look at your PGBUILDs and see if I can come up with a more acceptable solution for dealing with the dev-tools.
Comment by kachelaqa (kachelaqa) - Thursday, 11 December 2014, 20:53 GMT
Please find attached my PKGBUILD for the pyside dev tools, which I hope can provide the basis for an acceptable solution.

The package is split into python-pyside-tools, python2-pyside-tools and pyside-tools-common. I have tried to keep everything as simple as possible, and so I think I've managed to avoid all the "hackiness" of the current AUR PKGBUILDs. (NB: where necessary, the python2 version has been hardcoded as 2.7, since PEP 404 now guarantees there will never be an official 2.8 release).

The depends versioning is based on what's required by the CMakeLists.txt file.
   PKGBUILD (2.9 KiB)
Comment by Florian Pritz (bluewind) - Monday, 29 December 2014, 20:43 GMT
I've changed the pkgbuild slightly (missing makedep, please make sure to always build in clean chroots by using extra-x86_64-build from devtools) and moved it into [community]. Thank you.

Loading...