On 2022-12-22 07:03, Greg Minshall wrote:
has a build function that does `./configure --prefix=/usr`. is that safer than a plain `./configure`? or, does `make DESTDIR="${pkgdir}"/ install "strong enough" to (typically) deal with the default used by `./configure`?
Almost all autotools based configure scripts default to a prefix of /usr/local if not otherwise specified. This makes sense as a default for end users directly installing software from source onto their own systems, the base system of which is probably managed by some package manager. That being said /usr/local is not where the system package manager should ever put anything. Distro managed packages should always be in /usr and so forth. Hence almost all the PKGBUILD files in Arch official repos and the AUR have override build system defaults from source packages to set the prefix to be appropriate for package-manager managed paths rather than end user source installs.
right. but, is it okay to leave them there? it seems like having them there simplifies my life a bit (everything in a single git repository).
No, only the PKGBUILD, .SRCINFO, and any patches required to build and not available elsewhere should be part of the AUR repo.