From c5f6995aeb7f0622b63a736208850c9c86f38aad Mon Sep 17 00:00:00 2001 From: Dan McGee Date: Mon, 13 Dec 2010 22:35:24 -0600 Subject: Fix manpage wrap not at 80 characters Signed-off-by: Dan McGee --- doc/PKGBUILD.5.txt | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) (limited to 'doc/PKGBUILD.5.txt') diff --git a/doc/PKGBUILD.5.txt b/doc/PKGBUILD.5.txt index 684800eb..fdb868a9 100644 --- a/doc/PKGBUILD.5.txt +++ b/doc/PKGBUILD.5.txt @@ -269,16 +269,17 @@ will be run as the user calling makepkg. Package Splitting ----------------- -makepkg supports building multiple packages from a single PKGBUILD. This is achieved -by assigning an array of package names to the `pkgname` directive. Each split package -uses a corresponding packaging function with name `package_foo()`, where `foo` is the -name of the split package. - -All options and directives for the split packages default to the global values given -within the PKGBUILD. However, some of these can be overridden within each split -package's packaging function. The following variables can be overridden: `pkgver`, -`pkgrel`, `pkgdesc`, `arch`, `license`, `groups`, `depends`, `optdepends`, -`provides`, `conflicts`, `replaces`, `backup`, `options`, `install` and `changelog`. +makepkg supports building multiple packages from a single PKGBUILD. This is +achieved by assigning an array of package names to the `pkgname` directive. +Each split package uses a corresponding packaging function with name +`package_foo()`, where `foo` is the name of the split package. + +All options and directives for the split packages default to the global values +given within the PKGBUILD. However, some of these can be overridden within each +split package's packaging function. The following variables can be overridden: +`pkgver`, `pkgrel`, `pkgdesc`, `arch`, `license`, `groups`, `depends`, +`optdepends`, `provides`, `conflicts`, `replaces`, `backup`, `options`, +`install` and `changelog`. An optional global directive is available when building a split package: -- cgit v1.2.3 From ba45cb459084a0746e0005345b8c5483834d1ba2 Mon Sep 17 00:00:00 2001 From: Dan McGee Date: Mon, 13 Dec 2010 22:35:33 -0600 Subject: doc/PKGBUILD: document that functions run in -e mode Caught this noted on the forums, but it is definitely worth a note in the manpage as well. Signed-off-by: Dan McGee --- doc/PKGBUILD.5.txt | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) (limited to 'doc/PKGBUILD.5.txt') diff --git a/doc/PKGBUILD.5.txt b/doc/PKGBUILD.5.txt index fdb868a9..8bdb3c69 100644 --- a/doc/PKGBUILD.5.txt +++ b/doc/PKGBUILD.5.txt @@ -235,9 +235,11 @@ name. The syntax is: `source=('filename::url')`. build() Function ---------------- In addition to the above directives, the optional build() bash function usually -comprises the remainder of the PKGBUILD. This is directly sourced and executed by -makepkg, so anything that bash or the system has available is available for use -here. Be sure any exotic commands used are covered by `makedepends`. +comprises the remainder of the PKGBUILD. This is directly sourced and executed +by makepkg, so anything that bash or the system has available is available for +use here. The function is run in `bash -e` mode, meaning any command that exits +with a non-zero status will cause the function to exit. Be sure any exotic +commands used are covered by `makedepends`. All of the above variables such as `pkgname` and `pkgver` are available for use in the build function. In addition, makepkg defines three variables for your @@ -261,10 +263,12 @@ the build function. package() Function ------------------ -An optional package() function can be specified in addition to the build() function. -This function is run immediately after the build() function. When specified in -combination with the fakeroot BUILDENV option in linkman:makepkg.conf[5], fakeroot -usage will be limited to running the packaging stage. An existing build() function +An optional package() function can be specified in addition to the build() +function. This function is run immediately after the build() function. The +function is run in `bash -e` mode, meaning any command that exits with a +non-zero status will cause the function to exit. When specified in combination +with the fakeroot BUILDENV option in linkman:makepkg.conf[5], fakeroot usage +will be limited to running the packaging stage. An existing build() function will be run as the user calling makepkg. Package Splitting -- cgit v1.2.3