Most packages want to be helpful when installing them so they will have some dependency information in the
README or the
INSTALL file. Otherwise yes, checking the
configure script it the only real option (Note:
configure.log that enumerates dependencies, and several other configure scripts print a dependency summary at the end to make this easier for packagers).
For the problem at hand the README is most useful, it says:
- pcsclite 1.8.3 or above
- libusb 1.0.9 or above
Now, let us have a look at that. An AUR package can assume that
base-devel groups of packages are installed, which make things easier to reason about. Enumerating the dependencies we see:
pkg-config: is in
base-devel, we do not need to care about it.
perl: is part of
libusb 1.0.9 or above and
pcsclite 1.8.3 or above
pacman -Ss libusb
Library that provides generic access to USB devices
pacman -Ss pcsclite
PC/SC Architecture smartcard middleware library
The beauty of a rolling forward distribution is that you can assume that the user has the latest packages (if he is a sane user he will do
pacman -Syu before installing your AUR package). Therefore we can simply do (inside
Extra note: Sometimes it is not as easy to find the package a
INSTALL talks about. In this case google-fu is needed. Yet, arch also has
pkgfile which is the database of which files are in which packages.
For finding dependencies to be added to AUR packages I strongly recommend installing
pacman -S pkgfile
And then you can query suspicious packages for libraries, e.g.
pkgfile -l <package> | grep lib