simpler: in my PKGBUILD, do i need to list in any of the *depends any package that will *not* be used by makepkg? (motivation: the makefile in my package has uses other than building the package, and for some of *those* uses -- such a rolling a rev, etc. -- *do* need other packages.)

cheers, Greg

Hi Greg, it is "makedeps" not "maintenancedeps". Just put the stuff there that users need to pull sources and build a package. Your maintenance dependencies are not in scope of this. Best Georg

Hello, A package should only build one version of the codebase, so there is a few tags you can use: <packagename> on its own normally means the latest STABLE version <packagename>-beta or <packagename>-unstable etc can be made for unstable builds, such as prerelease builds. <packagename>-git is used to build the latest commit in the master branch. Whichever PKGBUILD you are making, you should specify ALL dependencies needed at the different stages, you can specify whether a dependency is needed just to build the package (such as a C compiler if the codebase is in C), and then the packages needed for the program to run, this is what people installing your package must also install as well (pacman calculates the dependencies itself when it installs a package, so the user never needs to worry about the dependencies you name in your MAKEPKG). In any case, ensure you name every dependency needed to build the package and also every dependency needed to run the package, this is all outlined within the arch wiki package on creating an AUR package. Hope this helps, Polarian