hi, Caleb, thanks very much.
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.
thanks. `./configure --prefix=/usr` it is.
No, only the PKGBUILD, .SRCINFO, and any patches required to build and not available elsewhere should be part of the AUR repo.
that is understandable, though a bit inconvenient in my case. how do people who have some automated process (like me with my Makefile) to produce PKGBUILD and .SRCINFO typically deal with this, structure things? (i don't *think* i saw any mention of this in the various wiki pages; apologies if i missed something.) my knee-jerk reaction is to have my private directory "A" with my Makefile produce PKGBUILD and .SRCINFO in a second directory/repository "B" which points at (has as a remote) AUR, and have some sort of "release" target in the Makefile in "A", which then builds PKGBUILD/.SRCINFO in "B", and runs `git -C "B"` to commit that, push to AUR. are there other schemes people use i might look at, think about, copy? again, thanks for the comments. cheers, Greg