As Allan pointed out, this actually ships with pacman (at least with Arch) and not necessarily with ABS or any other package. Signed-off-by: Dan McGee <dan@archlinux.org> --- doc/Makefile.am | 3 +++ doc/PKGBUILD.5.txt | 11 ++++------- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/Makefile.am b/doc/Makefile.am index d2f6b35..d5b7aad 100644 --- a/doc/Makefile.am +++ b/doc/Makefile.am @@ -86,10 +86,13 @@ endif html: $(HTML_DOCS) +pkgdatadir = ${datadir}/${PACKAGE} + ASCIIDOC_OPTS = \ -f asciidoc.conf \ -a pacman_version="$(REAL_PACKAGE_VERSION)" \ -a pacman_date="`date +%Y-%m-%d`" \ + -a pkgdatadir=$(pkgdatadir) \ -a sysconfdir=$(sysconfdir) A2X_OPTS = \ diff --git a/doc/PKGBUILD.5.txt b/doc/PKGBUILD.5.txt index 2d6589b..e62d520 100644 --- a/doc/PKGBUILD.5.txt +++ b/doc/PKGBUILD.5.txt @@ -20,13 +20,10 @@ This manual page is meant to describe general rules about PKGBUILDs. Once a PKGBUILD is written, the actual package is built using makepkg and installed with pacman. -NOTE: If you are using Arch Linux and have a local copy of the Arch Build -System (ABS) tree on your computer, or are using another distribution that -provides a similar tree of build files, you can copy the provided -PKGBUILD.proto file to a new package build directory and make customizations to -suit your needs. An up to date prototype file can also be found in the source -distribution of this package. - +NOTE: An example PKGBUILD, useful for reference, is located in '{pkgdatadir}'. +Also located there are other example files such as a ChangeLog and an install +script. You can copy the provided PKGBUILD.proto file to a new package build +directory and make customizations to suit your needs. Options and Directives ---------------------- -- 1.7.1