-
[options]
NoUpgrade = etc/passwd etc/group etc/shadow
NoUpgrade = etc/fstab
Include = /etc/pacman.d/current
[custom]
Server = file:///home/pkgs
CONFIG: OPTIONS
- DBPath = path/to/db/dir
-
Overrides the default location of the toplevel database directory. The default is
var/lib/pacman.
- HoldPkg = <package> [package] ...
-
If a user tries to --remove a package that's listed in HoldPkg, pacman
will ask for confirmation before proceeding.
- IgnorePkg = <package> [package] ...
-
Instructs pacman to ignore any upgrades for this package when performing a
--sysupgrade.
- Include = <path>
-
Include another config file. This config file can include repositories or
general configuration options.
- ProxyServer = <host|ip>[:port]
-
If set, pacman will use this proxy server for all ftp/http transfers.
- XferCommand = /path/to/command %u
-
If set, pacman will use this external program to download all remote files.
All instances of %u will be replaced with the URL to be downloaded. If
present, instances of %o will be replaced with the local filename, plus a
".part" extension, which allows programs like wget to do file resumes properly.
This option is useful for users who experience problems with pacman's built-in http/ftp
support, or need the more advanced proxy support that comes with utilities like
wget.
- NoPassiveFtp
-
Disables passive ftp connections when downloading packages. (aka Active Mode)
- NoUpgrade = <file> [file] ...
-
All files listed with a NoUpgrade directive will never be touched during a package
install/upgrade. Note: do not include the leading slash when specifying files.
- UseSyslog
-
Log action messages through syslog(). This will insert pacman log entries into your
/var/log/messages or equivalent.
- LogFile = /path/to/file
-
Log actions directly to a file, usually /var/log/pacman.log.
CONFIG: REPOSITORIES
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 Server 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 'file://' prefix, as
shown above.
USING YOUR OWN REPOSITORY
Let's say you have a bunch of custom packages in /home/pkgs and their respective PKGBUILD
files are all in /var/abs/local. All you need to do is generate a compressed package database
in the /home/pkgs directory so pacman can find it when run with --refresh.
-
# gensync /var/abs/local /home/pkgs/custom.db.tar.gz
The above command will read all PKGBUILD files in /var/abs/local and generate a compressed
database called /home/pkgs/custom.db.tar.gz. Note that the database must be of the form
{treename}.db.tar.gz, where {treename} is the name of the section defined in the
configuration file.
That's it! Now configure your custom 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.
SEE ALSO
makepkg is the package-building tool that comes with pacman.
AUTHOR
Judd Vinet <jvinet@zeroflux.org>
Index
- NAME
-
- SYNOPSIS
-
- DESCRIPTION
-
- OPERATIONS
-
- OPTIONS
-
- SYNC OPTIONS
-
- REMOVE OPTIONS
-
- QUERY OPTIONS
-
- HANDLING CONFIG FILES
-
- CONFIGURATION
-
- Example:
-
- CONFIG: OPTIONS
-
- CONFIG: REPOSITORIES
-
- USING YOUR OWN REPOSITORY
-
- SEE ALSO
-
- AUTHOR
-