You are not logged in.
Hi,
I've been building a few packages from AUR (through aura) lately that all required some python packages as dependencies. The thing is, I already installed some of these packages through pip, which prompted the installation of the AUR package to fail because the files were already present (I had to do a pip uninstall of the packages in question before the build)
So I have two questions:
1) Is there a recommended way to mark python packages as dependencies
and
2) What is the rationale for using the AUR version of these packages rather than having a requirements.txt file in the pip format
Thanks!
Offline
There's jsut https://wiki.archlinux.org/index.php/Py … Guidelines in the wiki.
Write a PKGBUILD and specify the dependencies there. In Arch we're using pacman to handle package updating and dependency resolving, so it makes sense to use packages rather than e.g. bare xpi plugins.
Offline
Write a PKGBUILD and specify the dependencies there. In Arch we're using pacman to handle package updating and dependency resolving, so it makes sense to use packages rather than e.g. bare xpi plugins.
Thanks for the info. But shouldn't there it be a mechanism to not install the arch version of a python pakage if the correct version has been installed using e.g. pip already?
Offline
karol wrote:Write a PKGBUILD and specify the dependencies there. In Arch we're using pacman to handle package updating and dependency resolving, so it makes sense to use packages rather than e.g. bare xpi plugins.
Thanks for the info. But shouldn't there it be a mechanism to not install the arch version of a python pakage if the correct version has been installed using e.g. pip already?
No. I think pip should be patched to inform pacman about its illegal operations in pacman territory.
Offline