On 19 September 2011 01:40, Jeremiah Dodds <jeremiah.dodds@xxxxxxxxx> wrote:
> If I'm wrong, and there's a standard way of doing this within
> PKGBUILDs, awesome.
> Assuming I'm not, I think the best you could do would be to not
> compile at all if the
> version you'd be compiling is the same as what's installed on your system, which
> you may already be doing.
You're not wrong, at least not on one account (the one you mentioned first).
1. Keep buildscripts locally and update the package manually (this is
a standard)
You will no longer depend on auto-update mechanisms (yaourt et
al) based on package updates from package maintainers, but keep the
buildscripts on your system for yourself. You will then initiate
makepkg as usual, and provided the PKGBUILD conforms to GIT packaging
standards, the checkout itself will always be there and will be
updated as and when needed.
2. There's no standard "caching" location for vcs packages
However, you can simply adopt your own convention across
PKGBUILDs that you use. One example is to have a standard location to
keep all vcs checkouts, and refer to the respective dir in there and
make your checks from within the PKGBUILD.
--
GPG/PGP ID: 8AADBB10
