You are not logged in.
I'm trying to install/build a package from AUR.
The AUR user guide recommends to run "makepkg -s", where -s uses pacman to install dependencies. However, when running this makepkg reports that it can't find a couple of the listed dependencies.
The dependencies seem to be not available in the "normal" repos but only in the AUR.
What is the recommended way to handle dependencies in AUR PKGBUILSs which are themselves only available in AUR?
Last edited by wierob (2013-05-31 22:54:46)
Offline
Install them the same way you are installing all your AUR packages; only in the order required to satisfy the dependency.
Offline
Grab the tarballs for the dependencies and then install them using makepkg. There are also AUR helpers out there, but I would encourage you to do it the manual way for at leat a few packages before you start relying on an AUR helper. That way, if you get yourself in a jam, you can still at least know how to use makepkg correctly if the issue involves AUR stuff (which it seems to pretty often from the threads we get around here).
Edit: If you want a shortcut for downloading the tarballs themselves (and the dependent tarballs), you can use falconindy's cower. It is in the AUR and you will have to build it, but that is all it does. It doesn't build the packages for you, and handles dependencies only as far as providing you with the PKGBUILDs you need to get there.
Last edited by WonderWoofy (2013-05-31 22:59:20)
Offline
Mh sounds fairly involved to install all dependencies and dependencies of dependencies (and ...) manually.
Offline
It depends how heavily you rely on the AUR. I only have ~30 packages and cower works perfectly well. In reality, it's something you do once; after that you are just updating...
Offline
I confess. I use packer. BUT... I know how to use the AUR and do write my own PKGBUILDS.
Before my kids were born, I was an active pilot; I sometimes used an autopilot -- but I could hand fly, and never trusted the autopilot for more than a few seconds at a time.
AUR helpers fall into the same bucket.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Ok. I feared that this would be the answer. I'm OK with doing things manually (that's why I'm trying arch). On the other hand, doing the same thing over and over again doesn't sound good. So I will take a (deeper) look into cower and other AUR helpers.
it's something you do once; after that you are just updating...
Isn't updating the same procedure over agin? Downloading, building/packaging and installing the packages and all its dependencies transitively.
Offline
Sort of: some of the dependencies will not have to be updated at the same time as the package. I can't remember the last time I had to update an AUR package and its dependencies simultaneously*...
* Unless, of course, there is a major lib rebuild required.
Offline
Because jasonwryan is the kind of guy he is, I will post this extremely relevant link on his behalf. Truer, saner, more-common-sense words have never been committed to The Intarwebz.
Offline
Mh sounds fairly involved to install all dependencies and dependencies of dependencies (and ...) manually.
It is somewhat involved but no more so than the old fashioned method of *nix installation: downloading a tarball, reading INSTALL and README, and running configure && make && make install.
FWIW, I keep track of dependencies through the use of recursive directories.
/var/abs/local/main-package
/var/abs/local/main-package/sub-package1
/var/abs/local/main-package/sub-package2
/var/abs/local/main-package/sub-package2/sub-sub-package
And so on...
Last edited by madalu (2013-06-01 12:15:21)
Offline