Package Details: python-p4python 2018.2.1743033-2

Git Clone URL: https://aur.archlinux.org/python-p4python.git (read-only, click to copy)
Package Base: python-p4python
Description: Interface to Perforce API for Python 3
Upstream URL: https://www.perforce.com/perforce/doc.current/manuals/p4script/03_python.html
Licenses: custom
Submitter: WhittlesJr
Maintainer: None
Last Packager: adytzu2007
Votes: 0
Popularity: 0.000000
First Submitted: 2017-05-05 18:59 (UTC)
Last Updated: 2021-12-15 11:51 (UTC)

Latest Comments

« First ‹ Previous 1 2

WhittlesJr commented on 2017-08-16 21:56 (UTC)

Mmk, so I'm sticking with one package for now, because the split package method is the standard. I added the appropriate makedepends, which should mitigate the issue maybe? For reference, my PKGBUILD is based off of https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=python-pyalsaaudio

WhittlesJr commented on 2017-08-16 21:34 (UTC)

Oh I think I see the issue... makepkg builds *both* packages no matter what. It's up to you to install either or both of course but the building is kind of out of our hands, huh... I wonder why the other PKGBUILDs all do it this way, given that restriction... I'm still looking into it. If I have to split the package, I will, but I don't wanna

WhittlesJr commented on 2017-08-16 21:06 (UTC)

1) Are you referring to the build() step, which builds both python2 and python3? I can see how that would cause problems... So I'll break that up. But I disagree that the python2 package should be submitted separately, as the majority of python-* PKGBUILDs are done this way. 2) Thanks for the tip. So I'll add openssl-1.0 as a dependency and include that build flag. Sound good?

f0ff886f commented on 2017-08-16 20:03 (UTC)

Thank you for the very fast update for the new version. I'd like to raise two issues with this project: 1) This tries to install p4python for python2 as well as python3. It should only install for python3, and the python2-p4python package, separately submitted to the AUR would be for python2 (makepkg breaks on systems without python2 installed). 2) This package needs a fix on current Arch installs for SSL. P4Python doesn't work with openssl 1.1, which is the default install on Arch. openssl-1.0 has the required headers and libraries, but in order to use the proper SSL version, you must pass "--ssl /usr/lib/openssl-1.0" to the "python setup.py build" in the PKGCONFIG.

« First ‹ Previous 1 2