Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorDan McGee <dan@archlinux.org>2007-03-01 20:16:15 +0000
committerDan McGee <dan@archlinux.org>2007-03-01 20:16:15 +0000
commit6fc69d52c8e77da7880426824e308a401293e525 (patch)
tree28acdee177901fcd563799fbbc2cca55f6ab56b2 /doc
parent06c82bfe87d71ae7084b367145cc30015e773549 (diff)
* Slight documentation update.
Diffstat (limited to 'doc')
-rw-r--r--doc/makepkg.816
1 files changed, 10 insertions, 6 deletions
diff --git a/doc/makepkg.8 b/doc/makepkg.8
index 22a39b47..1e0e2cd9 100644
--- a/doc/makepkg.8
+++ b/doc/makepkg.8
@@ -13,12 +13,16 @@ makepkg \- package build utility
.SH DESCRIPTION
\fBmakepkg\fP is a script to automate the building of packages. All it needs is
a build-capable Linux platform and a custom build script for each package you
-wish to build (known as a \fB\*(PB\fP). The advantage to a script-based build
-is that the work is only done once. Once you have the build script for a
-package, makepkg will do the rest: download and validate source files, check
-dependencies, configure the build-time settings, build the package, install the
-package into a temporary root, make customizations, generate meta-info, and
-package the whole thing up for \fBpacman\fP to use.
+wish to build (known as a \fB\*(PB\fP). See
+.BR \*(PB (5)
+for details on creating your own build scripts.
+
+The advantage to a script-based build is that the work is only done once. Once
+you have the build script for a package, makepkg will do the rest: download and
+validate source files, check dependencies, configure the build-time settings,
+build the package, install the package into a temporary root, make
+customizations, generate meta-info, and package the whole thing up for
+\fBpacman\fP to use.
\fBmakeworld\fP can be used to rebuild an entire package group or the entire
build tree. See \fBmakeworld --help\fP for syntax.