| index : pacman | |
| Archlinux32 fork of pacman | gitolite user |
| summaryrefslogtreecommitdiff |
| -rw-r--r-- | doc/PKGBUILD.5.txt | 15 |
diff --git a/doc/PKGBUILD.5.txt b/doc/PKGBUILD.5.txt index 2d6589b2..2f49ca57 100644 --- a/doc/PKGBUILD.5.txt +++ b/doc/PKGBUILD.5.txt @@ -20,12 +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 @@ -324,9 +322,8 @@ same directory as the PKGBUILD script. Then use the install directive: install=pkgname.install The install script does not need to be specified in the source array. A -template install file is available with the source distribution of this -program, or one may be provided by your distribution. For example, Arch Linux -provides prototype install files in the ABS tree. +template install file is available in '{pkgdatadir}' as 'proto.install' for +reference with all of the available functions defined. Development Directives |