<br><br>On Tue, Oct 8, 2013 at 3:45 PM, Allan McRae <allan@archlinux.org> wrote:<br>
<blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">On 08/10/13 23:26, Maxime Gauduin wrote:
<blockquote> Having separate prototypes for each VCS type is no longer relevant since
Pacman 4.1. Having a generic prototype for regular, bzr, git hg and svn
packages makes more sense. Left cvs, and darcs protos untouched as they
are not yet supported in Pacman.
Signed-off-by: Maxime Gauduin <alucryd@gmail.com>
---
prototypes/PKGBUILD-bzr.proto | 64 -------------------------
prototypes/PKGBUILD-git.proto | 64 -------------------------
prototypes/PKGBUILD-hg.proto | 65 -------------------------
prototypes/PKGBUILD-svn.proto | 63 ------------------------
prototypes/PKGBUILD.proto | 108 ++++++++++++++++++++++++++++++++++++++++++
5 files changed, 108 insertions(+), 256 deletions(-)
delete mode 100644 prototypes/PKGBUILD-bzr.proto
delete mode 100644 prototypes/PKGBUILD-git.proto
delete mode 100644 prototypes/PKGBUILD-hg.proto
delete mode 100644 prototypes/PKGBUILD-svn.proto
create mode 100644 prototypes/PKGBUILD.proto
</blockquote>
These are installed in /usr/share/pacman. You might notice a file by
that name already there and provided by pacman.
Allan
</div></blockquote><br><div>Indeed, my bad, didn't notice there already was a proto for a generic PKGBUILD. How about PKGBUILD-vcs.proto? Then I can just drop the whole 'VCS specific' paragraph and integrate it in the above. I'll also add a check function as to be closer to PKGBUILD.proto.</div><div>--</div><div>Maxime</div>