[aur-general] python packages as depends and easy_install
Hi, I am making a PKGBUILD for p and it requires pypump. Would it be ok to use easy_install-2.7 pypump in a build function or something? I would just make a pypump package, but I cloned the repository, and I'm not really sure where all that stuff goes lol. So, if using easy_install is ok, I'll just take the easy way out. Thanks Storm
22.6.2014 18:28:33 Storm Dragon kirjoitti:
I cloned the repository, and I'm not really sure where all that stuff goes lol.
pypump uses distutils, basically this just boils down to running the setup.py script. So you can just simply use the python proto PKGBUILD as a starting point. https://projects.archlinux.org/abs.git/tree/prototypes/PKGBUILD-python.proto
Would it be ok to use easy_install-2.7 pypump in a build function or
something?
No. Please make an actual package for pypump, and make p depend on pypump normally.
I would just make a pypump package, but I cloned the repository, and I'm
not really sure where all that stuff goes lol.
Don't install its files manually. Use the prototype PKGBUILD that Jesse linked to. (Thank you, Jesse.) If you are installing a Python 2 package, make sure to adjust the package slightly from the template: execute `python2 setup.py` instead of `python setup.py`, and adjust the package name accordingly. For yet more PKGBUILD examples, see some of my own. [1] [2] For more authoritative guidelines, see [3].
— Jeremy "Ichimonji10" Audet
[1] https://github.com/Ichimonji10/PKGBUILDs/blob/master/python-django-tables2/P... [2] https://github.com/Ichimonji10/PKGBUILDs/blob/master/python2-django-tables2/... [3] https://wiki.archlinux.org/index.php/Python_Package_Guidelines
Hi, The pypump docs say it works for all versions of python, 2.7, through 3.4 I think. I made the PKGBUILD using the python3 dependancy because I figure that is what most people will have by default. Does this PKGBUILD look ok? Thanks Storm On Sun, Jun 22, 2014 at 07:29:19PM -0400, Jeremy Audet wrote:
Would it be ok to use easy_install-2.7 pypump in a build function or
something?
No. Please make an actual package for pypump, and make p depend on pypump normally.
I would just make a pypump package, but I cloned the repository, and I'm
not really sure where all that stuff goes lol.
Don't install its files manually. Use the prototype PKGBUILD that Jesse linked to. (Thank you, Jesse.) If you are installing a Python 2 package, make sure to adjust the package slightly from the template: execute `python2 setup.py` instead of `python setup.py`, and adjust the package name accordingly. For yet more PKGBUILD examples, see some of my own. [1] [2] For more authoritative guidelines, see [3].
— Jeremy "Ichimonji10" Audet
[1] https://github.com/Ichimonji10/PKGBUILDs/blob/master/python-django-tables2/P... [2] https://github.com/Ichimonji10/PKGBUILDs/blob/master/python2-django-tables2/... [3] https://wiki.archlinux.org/index.php/Python_Package_Guidelines
On 22/06, Storm Dragon wrote:
Hi, The pypump docs say it works for all versions of python, 2.7, through 3.4 I think. I made the PKGBUILD using the python3 dependancy because I figure that is what most people will have by default. Does this PKGBUILD look ok? Thanks Storm
Hey,
It's mostly fine but http git URLs are prefered when possible since many people are behind firewalls that doesn't let the git protocol through.
I'd also prefer it if you remove the _pkgname variable since it's rather useless. The variable name is longer than the variable itself, and it doesn't change so it's largely useless.
Does this PKGBUILD look ok?
If pypump is a tool that users interact with directly (e.g. through the command line or a graphical program), then sure, that looks fine. However, if pypump is a library, then the package should be named python-pypump-git. I've had a quick look at the documentation for that project, and I believe it is intended for use as a library, so you should probably name the package python-pypump-git.
Otherwise, things look good to me.
— Jeremy "Ichimonji10" Audet
Hi, I used to use https for all my git packages. Then, someone told me I should use git:// lol. I searched for the email with that in it, but there are thousands of them and I couldn't find it. Anyway, Just to make absolutely sure, github offers https:i// or git://. So, any time there is a git package made from a project hosted at github use https:// in the source url, no exceptions? This means I have some packages to update. I made the other changes to p-git, but I wait to upload it til I get the reply to this. Thanks for all the help. Storm On Mon, Jun 23, 2014 at 12:20:28PM +0200, Johannes Löthberg wrote
On 22/06, Storm Dragon wrote:
Hi, The pypump docs say it works for all versions of python, 2.7, through 3.4 I think. I made the PKGBUILD using the python3 dependancy because I figure that is what most people will have by default. Does this PKGBUILD look ok? Thanks Storm
Hey,
It's mostly fine but http git URLs are prefered when possible since many people are behind firewalls that doesn't let the git protocol through.
I'd also prefer it if you remove the _pkgname variable since it's rather useless. The variable name is longer than the variable itself, and it doesn't change so it's largely useless.
-- Sincerely, Johannes Löthberg PGP Key ID: 3A9D0BB5
On 23/06, Storm Dragon wrote:
Hi, I used to use https for all my git packages. Then, someone told me I should use git:// lol. I searched for the email with that in it, but there are thousands of them and I couldn't find it. Anyway, Just to make absolutely sure, github offers https:i// or git://. So, any time there is a git package made from a project hosted at github use https:// in the source url, no exceptions? This means I have some packages to update. I made the other changes to p-git, but I wait to upload it til I get the reply to this. Thanks for all the help. Storm
You don't need to update them right away, but it's generally preferable. The git protocol runs over a port that is commonly closed in firewalls, while https is pretty much exclusively open everywhere.
Hi, I remember now why I was told to use git://. If I try the other way with https:// it wants a user name and password. I guess people who are behind a firewall that restricts git:// could edit the PKGBUILD so long as they have a github account? Thanks Storm On Mon, Jun 23, 2014 at 11:18:57PM +0200, Johannes Löthberg wrote:
On 23/06, Storm Dragon wrote:
Hi, I used to use https for all my git packages. Then, someone told me I should use git:// lol. I searched for the email with that in it, but there are thousands of them and I couldn't find it. Anyway, Just to make absolutely sure, github offers https:i// or git://. So, any time there is a git package made from a project hosted at github use https:// in the source url, no exceptions? This means I have some packages to update. I made the other changes to p-git, but I wait to upload it til I get the reply to this. Thanks for all the help. Storm
You don't need to update them right away, but it's generally preferable. The git protocol runs over a port that is commonly closed in firewalls, while https is pretty much exclusively open everywhere.
-- Sincerely, Johannes Löthberg PGP Key ID: 3A9D0BB5
https on Github shouldn't require a username and password. I do believe you'll need something like git+https declared in your git source so that makepkg will know it's a git package and how to build it. ~Kyle http://kyle.tk/
Hi, that's what I had: source=("p::git+https://github.com/xray7224/p.git") Thanks Storm On Mon, Jun 23, 2014 at 06:00:45PM -0400, Kyle wrote:
https on Github shouldn't require a username and password. I do believe you'll need something like git+https declared in your git source so that makepkg will know it's a git package and how to build it. ~Kyle http://kyle.tk/ -- "Kyle? ... She calls her cake, Kyle?" Out of This World, season 2 episode 21 - "The Amazing Evie"
participants (5)
-
Jeremy Audet
-
Jesse Jaara
-
Johannes Löthberg
-
Kyle
-
Storm Dragon