|
* Drop conflicts line, Arch guidelines explicitly say not to mark these
both ways and that VCS packages should have the conflict for the
stable release packages, not the other way around.
* Don't nuke the build dir, allows rebuilds. Using `makepkg -C` already
handles the details of doing a clean build (as does `makechrootpkg`).
When not using those options it's actually quite useful to be able to
run rebuilds to check that nothing changed but take advantage of the
build system's cache.
* Depend on freetype's provided soname. This is controversial in Arch
circles especially as most projects don't increment their SO version
numbers sanely. Most Arch packages do not provide soname information.
A handfull do, and freetype is one that does. This won't affect AUR
builders very much, but I host this package in a precompiled
repository and this dependency automatically version-locks this
package to the matching version of Freetype2. It doesn't need
recompiling for most Freetype2 updates, but if the soname version
changes then it does. This accomplishes that in a way that the regular
package dependency does not.
* Don't use verbose bash shell variable syntax. This is definitely not
an Arch guideline as they only require valid bash syntax and quoting
anything that does (or may) have spaces, but not using the braces
except when needed to disambiguate a variable or add flags is how the
`shellharden` utility outputs code. It's really convenient to be able
to run PKGBUILD files though it and let it rewrite anything that needs
fixing, so I tend to standardize on it's preferences even over my own.
|