1. It's a package - you install it as any other package. The introduction clearly states that The resulting package contains binary files and installation instructions; readily installed with pacman. and a link to the pacman article.

External links

One of the two links is redundant, is the same mentioned here
Tip: A prototype .install is provided at /usr/share/pacman/proto.install.
the second one should be added to proto installed by pacman package.

check / checkdepends

the default PKGBUILD in /usr/share/pacman now contains a check function and a checkdepends array. Some explanation would be nice.
--Oal 15:41, 26 July 2011 (EDT)

epoch

There is an epoch variable in the PKGBUILD.proto and an explanation here in the wiki, but for me at least the explanation doesn't cut it, I'd have no idea how to use it. I'm not sure that something that seems to be only meant for very special cases should be in the proto (which is meant for new packages, as I see it).
hollunder 12:20, 11 September 2011 (EDT)

package compression

Compression is IMO useless for game's package and almost nobody from aur is using this variable... And they are looking usually for info in archwiki ;)

See [3] for a couple ways to skin this cat. -- Karol 05:55, 12 December 2011 (EST)

package description

> Note: Do not follow this rule thoughtlessly when submitting packages to AUR. If package name
> differs from application name for some reason, inclusion of full name into description can be
> the only way to ensure that package can be found during search.

I never had trouble with pre-/postfixed application names so the note doesn't apply to this case. Does it? Slopjong 03:19, 11 July 2012 (CEST)

makedepends should not include base?

There is a warning not to include base-devel packages in makedepends, but should it also be said not to include base pacakges in makedepends (or even in depends)?