diff options
Diffstat (limited to 'doc/pacman.8.in')
| -rw-r--r-- | doc/pacman.8.in | 66 |
1 files changed, 50 insertions, 16 deletions
diff --git a/doc/pacman.8.in b/doc/pacman.8.in index dd3da750..d8bb26b7 100644 --- a/doc/pacman.8.in +++ b/doc/pacman.8.in @@ -1,4 +1,4 @@ -.TH pacman 8 "July 18, 2002" "pacman #VERSION#" "" +.TH pacman 8 "August 18, 2002" "pacman #VERSION#" "" .SH NAME pacman \- package manager utility .SH SYNOPSIS @@ -149,21 +149,55 @@ All three files are different. So we install the new file, but back up the old one to a .pacsave extension. This way the user can move the old configuration file back into place if he wishes. .SH CONFIGURATION -pacman will attempt to read \fI/etc/pacman.conf\fP each time it is invoked. Currently -the only options in it are for the --sync operation, but more may be added later. -.TP -.B "Sync_Tree_Name" -Sets the name of the package set you wish to follow. The common choices are \fIcurrent\fP -and \fIstable\fP. You could also specify a specific package version, eg, 0.3. -.TP -.B "Sync_Server" -This is the hostname of the ftp server that will be used for downloading lists and -packages. eg, \fIftp.ibiblio.org\fP. -.TP -.B "Sync_Tree_Path" -This is the full path name (on the ftp server) to the package tree you are following. -So if you are following \fIcurrent\fP, on \fIftp.ibiblio.org\fP, you would use -\fI/pub/linux/distributions/archlinux/current\fP. +pacman will attempt to read \fI/etc/pacman.conf\fP each time it is invoked. This +configuration file is divided into sections or \fIrepositories\fP. Each section +defines a package repository that pacman can use when searching for packages in +--sync mode. The exception to this is the \fIoptions\fP section, which defines +global options. +.TP +.SH Example: +.RS +.nf +[options] +NoUpgrade = etc/passed etc/group etc/shadow +NoUpgrade = etc/fstab + +[current] +Server = ftp://ftp.server.org/linux/archlinux/current +Server = ftp://ftp.mirror.com/arch/current + +[custom] +Server = local:///home/pkgs + +.fi +.RE +All files listed with a \fINoUpgrade\fP directive will never be touched during a package +install/upgrade. This directive is only valid in the options section. + +Each repository section defines a section name and at least one location where the packages +can be found. The section name is defined by the string within square brackets (eg, the two +above are 'current' and 'custom'). Locations are defined with the \fIServer\fP directive and +follow a URL naming structure. Currently only ftp is supported for remote servers. If you +want to use a local directory, you can specify the full path with a 'local://' prefix, as +shown above. +.SH USING YOUR OWN REPOSITORY +Let's say you have a bunch of custom packages in \fI/home/pkgs\fP and their respective PKGBUILD +files are all in \fI/usr/abs/local\fP. All you need to do is generate a compressed package database +in the \fI/home/pkgs\fP directory so pacman can find it when run with --refresh. + +.RS +.nf +# gensync /usr/abs/local /home/pkgs/custom.db.tar.gz +.fi +.RE + +The above command will read all PKGBUILD files in /usr/abs/local and generate a compressed +database called /home/pkgs/custom.db.tar.gz. Note that the database must be of the form +\fI{treename}.db.tar.gz\fP, where {treename} is the name of the section defined in the +configuration file. +That's it! Now configure your \fIcustom\fP section in the configuration file as shown in the +config example above. Pacman will now use your package repository. If you add new packages to +the repository, remember to re-generate the database and use pacman's --refresh option. .SH SEE ALSO \fBmakepkg\fP is the package-building tool that comes with pacman. .SH AUTHOR |