Git-Url:
http://git.frugalware.org/gitweb/gitweb.cgi?p=pacman-g2.git;a=commitdiff;h=190fbecbdf60c8408b9eecc96870823321b6774f
commit 190fbecbdf60c8408b9eecc96870823321b6774f
Author: Miklos Vajna <[EMAIL PROTECTED]>
Date: Fri Nov 9 20:19:40 2007 +0100
converted pacman-g2 manpage to asciidoc
diff --git a/doc/pacman-g2.8 b/doc/pacman-g2.8
deleted file mode 100644
index 47d4f4a..0000000
--- a/doc/pacman-g2.8
+++ /dev/null
@@ -1,385 +0,0 @@
-.TH pacman-g2 8 "Feb 23, 2007" "Frugalware User Manual" ""
-.SH NAME
-pacman-g2 \- package manager utility
-.SH SYNOPSIS
-\fBpacman-g2 <operation> [options] <package> [package] ...\fP
-.SH DESCRIPTION
-\fBpacman-g2\fP is a \fIpackage management\fP utility that tracks installed
-packages on a linux system. It has simple dependency support and the ability
-to connect to a remote ftp server and automatically upgrade packages on
-the local system. pacman-g2 package are \fIbzipped tar\fP format.
-.SH OPERATIONS
-.TP
-.B "\-A, \-\-add"
-Add a package to the system. Package will be uncompressed
-into the installation root and the database will be updated.
-.TP
-.B "\-F, \-\-freshen"
-This is like --upgrade except that, unlike --upgrade, this will only
-upgrade packages that are already installed on your system.
-.TP
-.B "\-Q, \-\-query"
-Query the package database. This operation allows you to
-view installed packages and their files, as well as meta-info
-about individual packages (dependencies, conflicts, install date,
-build date, size). This can be run against the local package
-database or can be used on individual .fpm packages. See
-\fBQUERY OPTIONS\fP below.
-.TP
-.B "\-c, \-\-changelog"
-View the changelog of a package.
-.TP
-.B "\-R, \-\-remove"
-Remove a package from the system. Files belonging to the
-specified package will be deleted, and the database will
-be updated. Most configuration files will be saved with a
-\fI.pacsave\fP extension unless the \fB--nosave\fP option was
-used.
-.TP
-.B "\-S, \-\-sync"
-Synchronize packages. With this function you can install packages
-directly from the ftp servers, complete with all dependencies required
-to run the packages. For example, \fBpacman-g2 -S qt\fP will download
-qt and all the packages it depends on and install them. You could also use
-\fBpacman-g2 -Su\fP to upgrade all packages that are out of date (see below).
-.TP
-.B "\-U, \-\-upgrade"
-Upgrade a package. This is essentially a "remove-then-add"
-process. See \fBHANDLING CONFIG FILES\fP for an explanation
-on how pacman-g2 takes care of config files.
-.TP
-.B "\-V, \-\-version"
-Display version and exit.
-.TP
-.B "\-h, \-\-help"
-Display syntax for the given operation. If no operation was
-supplied then the general syntax is shown.
-.SH OPTIONS
-.TP
-.B "\-d, \-\-nodeps"
-Skips all dependency checks. Normally, pacman-g2 will always check
-a package's dependency fields to ensure that all dependencies are
-installed and there are no package conflicts in the system. This
-switch disables these checks.
-.TP
-.B "\-f, \-\-force"
-Bypass file conflict checks, overwriting conflicting files. If the
-package that is about to be installed contains files that are already
-installed, this option will cause all those files to be overwritten.
-This option should be used with care, ideally not at all.
-.TP
-.B "\-r, \-\-root <path>"
-Specify alternative installation root (default is "/"). This
-should \fInot\fP be used as a way to install software into
-e.g. /usr/local instead of /usr. Instead this should be used
-if you want to install a package on a temporary mounted partition,
-which is "owned" by another system. By using this option you not only
-specify where the software should be installed, but you also
-specify which package database to use.
-.TP
-.B "\-v, \-\-verbose"
-Output more status and error messages.
-.TP
-.B "\-\-config <path>"
-Specify an alternate configuration file.
-.TP
-.B "\-\-noconfirm"
-Bypass any and all "Are you sure?" messages. It's not a good idea to do this
-unless you want to run pacman-g2 from a script.
-.TP
-.B "\-\-ask <number>"
-Finetune the --noconfirm switch by not answering "yes" to all libpacman
-questions, but you are able to specify yes/no for all type of libpacman
-questions. The types are the followings:
-.nf
-The given package is in IgnorePkg. (1)
-Replace package foo with bar? (2)
-foo conflicts with bar. Remove bar? (4)
-Do you want to delete the corrupted package? (8)
-Local version is newer. (16)
-Local version is up to date. (32)
-.fi
-Select for what types do you want to answer yes, sum up the values and use the
-result as a parameter to this option.
-.TP
-.B "\-\-noprogressbar"
-Do not show a progress bar when downloading files. This can be useful for
-scripts that call pacman-g2 and capture the output.
-.SH SYNC OPTIONS
-.TP
-.B "\-c, \-\-clean"
-Remove old packages from the cache. When pacman-g2 downloads packages,
-it saves them in \fI/var/cache/pacman/pkg\fP. If you need to free up
-diskspace, you can remove these packages by using the --clean option.
-Using one --clean (or -c) switch will only remove \fIold\fP packages.
-Use it twice to remove \fIall\fP packages from the cache.
-.TP
-.B "\-e, \-\-dependsonly"
-Don't install the packages itself, only their dependencies. This can be
-handy if you want to install the packages themselves with different
-options or from source.
-.TP
-.B "\-g, \-\-groups"
-Display all the members for each package group specified. If no group
-names are provided, all groups will be listed.
-.TP
-.B "\-i, \-\-info"
-Display dependency information for a given package. This will search
-through all repositories for a matching package and display the
-dependencies, conflicts, etc.
-.TP
-.B "\-l, \-\-list"
-List all files in the specified repositories. Multiple repositories can
-be specified on the command line.
-.TP
-.B "\-p, \-\-print-uris"
-Print out URIs for each package that will be installed, including any
-dependencies that have yet to be installed. These can be piped to a
-file and downloaded at a later time, using a program like wget.
-.TP
-.B "\-s, \-\-search <regexp>"
-This will search each package in the package list for names or descriptions
-that contains <regexp>.
-.TP
-.B "\-u, \-\-sysupgrade"
-Upgrades all packages that are out of date. pacman-g2 will examine every
-package installed on the system, and if a newer package exists on the
-server it will upgrade. pacman-g2 will present a report of all packages
-it wants to upgrade and will not proceed without user confirmation.
-Dependencies are automatically resolved at this level and will be
-installed/upgraded if necessary.
-.TP
-.B "\-w, \-\-downloadonly"
-Retrieve all packages from the server, but do not install/upgrade anything.
-.TP
-.B "\-y, \-\-refresh"
-Download a fresh copy of the master package list from the ftp server
-defined in \fI/etc/pacman.conf\fP. This should typically be used each
-time you use \fB--sysupgrade\fP.
-.TP
-.B "\-\-ignore <pkg>"
-This option functions exactly the same as the \fBIgnorePkg\fP configuration
-directive. Sometimes it can be handy to skip some package updates without
-having to edit \fIpacman.conf\fP each time.
-.SH REMOVE OPTIONS
-.TP
-.B "\-c, \-\-cascade"
-Remove all target packages, as well as all packages that depend on one
-or more target packages. This operation is recursive.
-.TP
-.B "\-k, \-\-keep"
-Removes the database entry only. Leaves all files in place.
-.TP
-.B "\-n, \-\-nosave"
-Instructs pacman-g2 to ignore file backup designations. Normally, when
-a file is about to be \fIremoved\fP from the system the database is first
-checked to see if the file should be renamed to a .pacsave extension. If
-\fB--nosave\fP is used, these designations are ignored and the files are
-removed.
-.TP
-.B "\-s, \-\-recursive"
-For each target specified, remove it and all its dependencies, provided
-that (A) they are not required by other packages; and (B) they were not
-explicitly installed by the user.
-This option is analagous to a backwards --sync operation.
-.SH QUERY OPTIONS
-.TP
-.B "\-e, \-\-orphans"
-List all packages that were installed as a dependency (ie, not
-installed explicitly) and are not required by any other
-packages.
-.TP
-.B "\-g, \-\-groups"
-Display all groups that a specified package is part of. If no package
-names are provided, all groups and members will be listed.
-.TP
-.B "\-i, \-\-info"
-Display information on a given package. If it is used with the \fB-p\fP
-option then the .PKGINFO file will be printed.
-.TP
-.B "\-l, \-\-list"
-List all files owned by <package>. Multiple packages can be specified on
-the command line.
-.TP
-.B "\-m, \-\-foreign"
-List all packages that were not found in the sync database(s). Typically these
-are packages that were downloaded manually and installed with --add.
-.TP
-.B "\-o, \-\-owns <file>"
-Search for the package that owns <file>.
-.TP
-.B "\-p, \-\-file"
-Tells pacman-g2 that the package supplied on the command line is a
-file, not an entry in the database. Pacman will decompress the
-file and query it. This is useful with \fB--info\fP and \fB--list\fP.
-.TP
-.B "\-s, \-\-search <regexp>"
-This will search each locally-installed package for names or descriptions
-that contains <regexp>.
-.TP
-.B "\-t, \-\-test"
-Tests the local database, by searching for missing informations. Example:
-
-.nf
-$ pacman-g2 -Qt
-:: zip-2.32-1: file list is missing
-.fi
-
-The recommended method in this case is to remove the database entry:
-
-# rm -rf /var/lib/pacman/local/zip-2.32-1
-
-and forcing the reinstall of the package:
-
-# pacman -Sf zip --noconfirm
-.TP
-.B "\-\-nointegrity"
-Skip the SHA1 integrity check for the downloaded packages.
-.SH HANDLING CONFIG FILES
-pacman-g2 uses the same logic as rpm to determine action against files
-that are designated to be backed up. During an upgrade, it uses 3
-md5 hashes for each backup file to determine the required action:
-one for the original file installed, one for the new file that's about
-to be installed, and one for the actual file existing on the filesystem.
-After comparing these 3 hashes, the follow scenarios can result:
-.TP
-original=\fBX\fP, current=\fBX\fP, new=\fBX\fP
-All three files are the same, so we win either way. Install the new file.
-.TP
-original=\fBX\fP, current=\fBX\fP, new=\fBY\fP
-The current file is un-altered from the original but the new one is
-different. Since the user did not ever modify the file, and the new
-one may contain improvements/bugfixes, we install the new file.
-.TP
-original=\fBX\fP, current=\fBY\fP, new=\fBX\fP
-Both package versions contain the exact same file, but the one
-on the filesystem has been modified since. In this case, we leave
-the current file in place.
-.TP
-original=\fBX\fP, current=\fBY\fP, new=\fBY\fP
-The new one is identical to the current one. Win win. Install the new file.
-.TP
-original=\fBX\fP, current=\fBY\fP, new=\fBZ\fP
-All three files are different, so we install the new file with a .pacnew
-extension and warn the user, so she can manually move the file into place
-after making any necessary customizations.
-.SH CONFIGURATION
-pacman-g2 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-g2 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]
-HoldPkg = pacman-g2 glibc bash coreutils
-HoldPkg = chkconfig
-
-Include = /etc/pacman.d/frugalware-current
-
-[custom]
-Server = file:///home/pkgs
-
-.fi
-.RE
-.SH CONFIG: OPTIONS
-.TP
-.B "DBPath = path/to/db/dir"
-Overrides the default location of the toplevel database directory. The
default is
-\fIvar/lib/pacman\fP.
-.TP
-.B "CacheDir = path/to/cache/dir"
-Overrides the default location of the package cache directory. The default is
-\fIvar/cache/pacman\fP.
-.TP
-.B "HoldPkg = <package> [package] ..."
-If a user tries to \fB--remove\fP a package that's listed in HoldPkg, pacman-g2
-will ask for confirmation before proceeding.
-.TP
-.B "IgnorePkg = <package> [package] ..."
-Instructs pacman-g2 to ignore any upgrades for this package when performing a
-\fB--sysupgrade\fP.
-.TP
-.B "UpgradeDelay = <number>"
-Upgrade only the packages that are at least <number> days old when
-performing a \fB--sysupgrade\fP.
-.TP
-.B "OldDelay = <number>"
-Issue a warning when you install a package, but the local sync database (which
-can be upgraded using \fB-Sy\fP) haven't been updated for <number> days.
-.TP
-.B "MaxTries = <number>"
-Try to download packages <number> times. This is useful in case you have a bad
-internet connection and your packages often get corrupted during the download.
-.TP
-.B "Include = <path>"
-Include another config file. This config file can include repositories or
-general configuration options.
-.TP
-.B "ProxyServer = <host|ip>[:port]"
-If set, pacman-g2 will use this proxy server for all ftp/http transfers.
-.TP
-.B "XferCommand = /path/to/command %u"
-If set, pacman-g2 will use this external program to download all remote files.
-All instances of \fB%u\fP will be replaced with the URL to be downloaded. If
-present, instances of \fB%o\fP 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-g2's
built-in http/ftp
-support, or need the more advanced proxy support that comes with utilities like
-wget.
-.TP
-.B "NoPassiveFtp"
-Disables passive ftp connections when downloading packages. (aka Active Mode)
-.TP
-.B "NoUpgrade = <file> [file] ..."
-All files listed with a \fBNoUpgrade\fP directive will never be touched during
a package
-install/upgrade. \fINote:\fP do not include the leading slash when specifying
files.
-.TP
-.B "NoExtract = <file> [file] ..."
-All files listed with a \fBNoExtract\fP directive will never be extracted from
-a package into the filesystem. This can be useful when you don't want part of
-a package to be installed. For example, if your httpd root uses an index.php,
-then you would not want the index.html file to be extracted from the apache
-package.
-.TP
-.B "UseSyslog"
-Log action messages through syslog(). This will insert pacman-g2 log entries
into your
-/var/log/messages or equivalent.
-.TP
-.B "LogFile = /path/to/file"
-Log actions directly to a file, usually /var/log/pacman-g2.log.
-
-.SH 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
\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 'file://'
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 FrugalBuild
-files are all in \fI/var/fst/local\fP. All you need to do is generate a
compressed package database
-in the \fI/home/pkgs\fP directory so pacman-g2 can find it when run with
--refresh.
-
-.RS
-.nf
-# gensync /var/fst/local /home/pkgs/custom.fdb
-.fi
-.RE
-
-The above command will read all FrugalBuild files in /var/fst/local and
generate a compressed
-database called /home/pkgs/custom.fdb. Note that the database must be of the
form
-\fI{treename}.fdb\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-g2's
--refresh option.
-.SH SEE ALSO
-\fBmakepkg\fP is the package-building tool that comes with pacman-g2.
-.SH AUTHOR
-.nf
-See /usr/share/doc/pacman-g2-*/AUTHORS.
-.fi
diff --git a/doc/pacman-g2.txt b/doc/pacman-g2.txt
new file mode 100644
index 0000000..c1a391a
--- /dev/null
+++ b/doc/pacman-g2.txt
@@ -0,0 +1,403 @@
+= pacman-g2(8)
+
+== NAME
+
+pacman-g2 - package manager utility
+
+== SYNOPSIS
+
+pacman-g2 <operation> [options] <package> [package] ...
+
+== DESCRIPTION
+
+pacman-g2 is a package management utility that tracks installed packages on a
+linux system. It has simple dependency support and the ability to connect to a
+remote ftp server and automatically upgrade packages on the local system.
+pacman-g2 packages are in a bzipped tar format.
+
+== OPERATIONS
+
+-A, --add::
+ Add a package to the system. Package will be uncompressed into the
installation
+ root and the database will be updated.
+
+-F, --freshen::
+ This is like --upgrade except that, unlike --upgrade, this will only
upgrade
+ packages that are already installed on your system.
+
+-Q, --query::
+ Query the package database. This operation allows you to view installed
+ packages and their files, as well as meta-info about individual packages
+ (dependencies, conflicts, install date, build date, size). This can be
run
+ against the local package database or can be used on individual .fpm
packages.
+ See QUERY OPTIONS below.
+
+-R, --remove::
+ Remove a package from the system. Files belonging to the specified
package will
+ be deleted, and the database will be updated. Most configuration files
will be
+ saved with a .pacsave extension unless the --nosave option was used.
+
+-S, --sync::
+ Synchronize packages. With this function you can install packages
directly from
+ the ftp servers, complete with all dependencies required to run the
packages.
+ For example, pacman-g2 -S qt will download qt and all the packages it
depends
+ on and install them. You could also use pacman-g2 -Su to upgrade all
packages
+ that are out of date (see below).
+
+-U, --upgrade::
+ Upgrade a package. This is essentially a "remove-then-add" process. See
+ HANDLING CONFIG FILES for an explanation on how pacman-g2 takes care of
config
+ files.
+
+-V, --version::
+ Display version and exit.
+
+-h, --help::
+ Display syntax for the given operation. If no operation was supplied
then the
+ general syntax is shown.
+
+== OPTIONS
+
+-d, --nodeps::
+ Skips all dependency checks. Normally, pacman-g2 will always check a
package's
+ dependency fields to ensure that all dependencies are installed and
there are
+ no package conflicts in the system. This switch disables these checks.
+
+-f, --force::
+ Bypass file conflict checks, overwriting conflicting files. If the
package that
+ is about to be installed contains files that are already installed,
this option
+ will cause all those files to be overwritten. This option should be
used with
+ care, ideally not at all.
+
+-r, --root <path>::
+ Specify alternative installation root (default is "/"). This should not
be used
+ as a way to install software into e.g. /usr/local instead of /usr.
Instead this
+ should be used if you want to install a package on a temporary mounted
+ partition, which is "owned" by another system. By using this option you
not
+ only specify where the software should be installed, but you also
specify which
+ package database to use.
+
+-v, --verbose::
+ Output more status and error messages.
+
+--config <path>::
+ Specify an alternate configuration file.
+
+--noconfirm::
+ Bypass any and all "Are you sure?" messages. It's not a good idea to do
this
+ unless you want to run pacman-g2 from a script.
+
+--ask <number>::
+ Finetune the --noconfirm switch by not answering "yes" to all libpacman
+ questions, but you are able to specify yes/no for all type of them. The
types
+ are the followings:
+
+ * The given package is in IgnorePkg. (1)
+ * Replace package foo with bar? (2)
+ * foo conflicts with bar. Remove bar? (4)
+ * Do you want to delete the corrupted package? (8)
+ * Local version is newer. (16)
+ * Local version is up to date. (32)
+
+ Select for what types do you want to answer yes, sum up the values and
use the
+ result as a parameter to this option.
+
+--noprogressbar::
+ Do not show a progress bar when downloading files. This can be useful
for
+ scripts that call pacman-g2 and capture the output.
+
+== SYNC OPTIONS
+
+-c, --clean::
+ Remove old packages from the cache. When pacman-g2 downloads packages,
it saves
+ them in /var/cache/pacman/pkg. If you need to free up diskspace, you
can remove
+ these packages by using the --clean option. Using one --clean (or -c)
switch
+ will only remove old packages. Use it twice to remove all packages from
the
+ cache.
+
+-e, --dependsonly::
+ Don't install the packages itself, only their dependencies. This can be
handy
+ if you want to install the packages themselves with different options
or from
+ source.
+
+-g, --groups::
+ Display all the members for each package group specified. If no group
names are
+ provided, all groups will be listed.
+
+-i, --info::
+ Display dependency information for a given package. This will search
through
+ all repositories for a matching package and display the dependencies,
+ conflicts, etc.
+
+-l, --list::
+ List all files in the specified repositories. Multiple repositories can
be
+ specified on the command line.
+
+-p, --print-uris::
+ Print out URIs for each package that will be installed, including any
+ dependencies that have yet to be installed. These can be piped to a
file and
+ downloaded at a later time, using a program like wget.
+
+-s, --search <regexp>::
+ This will search each package in the package list for names or
descriptions
+ that contains <regexp>.
+
+-u, --sysupgrade::
+ Upgrades all packages that are out of date. pacman-g2 will examine every
+ package installed on the system, and if a newer package exists on the
server it
+ will upgrade. pacman-g2 will present a report of all packages it wants
to
+ upgrade and will not proceed without user confirmation. Dependencies are
+ automatically resolved at this level and will be installed/upgraded if
+ necessary.
+
+-w, --downloadonly::
+ Retrieve all packages from the server, but do not install/upgrade
anything.
+
+-y, --refresh::
+ Download a fresh copy of the master package list from the ftp server
defined in
+ /etc/pacman.conf. This should typically be used each time you use
+ --sysupgrade.
+
+--ignore <pkg>::
+ This option functions exactly the same as the IgnorePkg configuration
+ directive. Sometimes it can be handy to skip some package updates
without
+ having to edit pacman.conf each time.
+
+== REMOVE OPTIONS
+
+-c, --cascade::
+ Remove all target packages, as well as all packages that depend on one
or more
+ target packages. This operation is recursive.
+
+-k, --keep::
+ Removes the database entry only. Leaves all files in place.
+
+-n, --nosave::
+ Instructs pacman-g2 to ignore file backup designations. Normally, when
a file
+ is about to be removed from the system the database is first checked to
see if
+ the file should be renamed to a .pacsave extension. If --nosave is
used, these
+ designations are ignored and the files are removed.
+
+-s, --recursive::
+ For each target specified, remove it and all its dependencies, provided
that
+ (A) they are not required by other packages; and (B) they were not
explicitly
+ installed by the user. This option is analagous to a backwards --sync
+ operation.
+
+== QUERY OPTIONS
+
+-c, --changelog::
+ View the changelog of a package.
+
+-e, --orphans::
+ List all packages that were installed as a dependency (ie, not installed
+ explicitly) and are not required by any other packages.
+
+-g, --groups::
+ Display all groups that a specified package is part of. If no package
names are
+ provided, all groups and members will be listed.
+
+-i, --info::
+ Display information on a given package. If it is used with the -p
option then
+ the .PKGINFO file will be printed.
+
+-l, --list::
+ List all files owned by <package>. Multiple packages can be specified
on the
+ command line.
+
+-m, --foreign::
+ List all packages that were not found in the sync database(s).
Typically these
+ are packages that were downloaded manually and installed with --add.
+
+-o, --owns <path>::
+ Search for the package that owns a given file or directory.
+
+-p, --file::
+ Tells pacman-g2 that the package supplied on the command line is a
file, not an
+ entry in the database. Pacman will decompress the file and query it.
This is
+ useful with --info and --list.
+
+-s, --search <regexp>::
+ This will search each locally-installed package for names or
descriptions that
+ contains <regexp>.
+
+-t, --test::
+ Tests the local database, by searching for missing informations.
Example:
+
+ ----
+ $ pacman-g2 -Qt
+ :: zip-2.32-1: file list is missing
+ ----
+
+ The recommended method in this case is to remove the database entry:
+
+ ----
+ # rm -rf /var/lib/pacman/local/zip-2.32-1
+ ----
+
+ and forcing the reinstall of the package:
+
+ ----
+ # pacman-g2 -Sf zip --noconfirm
+ ----
+
+--nointegrity::
+ Skip the SHA1 integrity check for the downloaded packages.
+
+== HANDLING CONFIG FILES
+
+pacman-g2 uses the same logic as rpm to determine action against files that are
+designated to be backed up. During an upgrade, it uses 3 md5 hashes for each
+backup file to determine the required action: one for the original file
+installed, one for the new file that's about to be installed, and one for the
+actual file existing on the filesystem. After comparing these 3 hashes, the
+follow scenarios can result:
+
+original=X, current=X, new=X::
+ All three files are the same, so we win either way. Install the new
file.
+
+original=X, current=X, new=Y::
+ The current file is un-altered from the original but the new one is
different.
+ Since the user did not ever modify the file, and the new one may contain
+ improvements/bugfixes, we install the new file.
+
+original=X, current=Y, new=X::
+ Both package versions contain the exact same file, but the one on the
+ filesystem has been modified since. In this case, we leave the current
file in
+ place.
+
+original=X, current=Y, new=Y::
+ The new one is identical to the current one. Win win. Install the new
file.
+
+original=X, current=Y, new=Z::
+ All three files are different, so we install the new file with a .pacnew
+ extension and warn the user, so she can manually move the file into
place after
+ making any necessary customizations.
+
+== CONFIGURATION
+
+pacman-g2 will attempt to read /etc/pacman.conf each time it is invoked. This
+configuration file is divided into sections or repositories. Each section
+defines a package repository that pacman-g2 can use when searching for packages
+in --sync mode. The exception to this is the options section, which defines
+global options.
+
+Example:
+
+----
+[options]
+HoldPkg = pacman-g2 glibc bash coreutils
+HoldPkg = chkconfig
+
+Include = /etc/pacman.d/frugalware-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.
+
+CacheDir = path/to/cache/dir::
+ Overrides the default location of the package cache directory. The
default is
+ var/cache/pacman.
+
+HoldPkg = <package> [package] ...::
+ If a user tries to --remove a package that's listed in HoldPkg,
pacman-g2 will
+ ask for confirmation before proceeding.
+
+IgnorePkg = <package> [package] ...::
+ Instructs pacman-g2 to ignore any upgrades for this package when
performing a
+ --sysupgrade.
+
+UpgradeDelay = <number>::
+ Upgrade only the packages that are at least <number> days old when
performing a
+ --sysupgrade.
+
+OldDelay = <number>::
+ Issue a warning when you install a package, but the local sync database
(which
+ can be upgraded using -Sy) haven't been updated for <number> days.
+
+MaxTries = <number>::
+ Try to download packages <number> times. This is useful in case you
have a bad
+ internet connection and your packages often get corrupted during the
download.
+
+Include = <path>::
+ Include another config file. This config file can include repositories
or
+ general configuration options.
+
+ProxyServer = <host|ip>[:port]::
+ If set, pacman-g2 will use this proxy server for all ftp/http transfers.
+
+XferCommand = /path/to/command %u::
+ If set, pacman-g2 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-g2's
+ built-in http/ftp support, or need the more advanced proxy support that
comes
+ with utilities like curl.
+
+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.
+
+NoExtract = <file> [file] ...::
+ All files listed with a NoExtract directive will never be extracted
from a
+ package into the filesystem. This can be useful when you don't want
part of a
+ package to be installed. For example, if your httpd root uses an
index.php,
+ then you would not want the index.html file to be extracted from the
apache
+ package.
+
+UseSyslog::
+ Log action messages through *syslog*(2). This will insert pacman-g2 log
entries
+ into your /var/log/messages or equivalent.
+
+LogFile = /path/to/file::
+ Log actions directly to a file, usually /var/log/pacman-g2.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 FrugalBuild files are all in /var/fst/local. All you need to do is
+generate a compressed package database in the /home/pkgs directory so pacman-g2
+can find it when run with --refresh.
+
+----
+# gensync /var/fst/local /home/pkgs/custom.fdb
+----
+
+The above command will read all FrugalBuild files in /var/fst/local and
+generate a compressed database called /home/pkgs/custom.fdb. Note that the
+database must be of the form {treename}.fdb, 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-g2's --refresh
+option.
+
+== SEE ALSO
+
+*makepkg*(8)
+
+== AUTHORS
+
+See /usr/share/doc/pacman-g2-*/AUTHORS.
_______________________________________________
Frugalware-git mailing list
Frugalware-git@frugalware.org
http://frugalware.org/mailman/listinfo/frugalware-git
