Pacman-dev

Download

pacman-dev@lists.archlinux.org

February 2007

30 participants
271 discussions

[pacman-dev] CVS update of pacman-lib (4 files)
by dan＠archlinux.org 08 Feb '07

08 Feb '07

Date: Thursday, February 8, 2007 @ 00:36:26 Author: dan Path: /home/cvs-pacman/pacman-lib Added: lib/libalpm/po/remove-potcdate.sin (1.1) src/pacman/po/remove-potcdate.sin (1.1) Modified: lib/libalpm/po/.cvsignore (1.1 -> 1.2) src/pacman/po/.cvsignore (1.1 -> 1.2) * Oops. Added some files to make "make update-po" work. ------------------------------------+ lib/libalpm/po/.cvsignore | 2 ++ lib/libalpm/po/remove-potcdate.sin | 19 +++++++++++++++++++ src/pacman/po/.cvsignore | 2 ++ src/pacman/po/remove-potcdate.sin | 19 +++++++++++++++++++ 4 files changed, 42 insertions(+) Index: pacman-lib/lib/libalpm/po/.cvsignore diff -u pacman-lib/lib/libalpm/po/.cvsignore:1.1 pacman-lib/lib/libalpm/po/.cvsignore:1.2 --- pacman-lib/lib/libalpm/po/.cvsignore:1.1 Tue Jan 16 22:40:09 2007 +++ pacman-lib/lib/libalpm/po/.cvsignore Thu Feb 8 00:36:26 2007 @@ -4,3 +4,5 @@ POTFILES stamp-po +remove-potcdate.sin +remove-potcdate.sed Index: pacman-lib/lib/libalpm/po/remove-potcdate.sin diff -u /dev/null pacman-lib/lib/libalpm/po/remove-potcdate.sin:1.1 --- /dev/null Thu Feb 8 00:36:26 2007 +++ pacman-lib/lib/libalpm/po/remove-potcdate.sin Thu Feb 8 00:36:26 2007 @@ -0,0 +1,19 @@ +# Sed script that remove the POT-Creation-Date line in the header entry +# from a POT file. +# +# The distinction between the first and the following occurrences of the +# pattern is achieved by looking at the hold space. +/^"POT-Creation-Date: .*"$/{ +x +# Test if the hold space is empty. +s/P/P/ +ta +# Yes it was empty. First occurrence. Remove the line. +g +d +bb +:a +# The hold space was nonempty. Following occurrences. Do nothing. +x +:b +} Index: pacman-lib/src/pacman/po/.cvsignore diff -u pacman-lib/src/pacman/po/.cvsignore:1.1 pacman-lib/src/pacman/po/.cvsignore:1.2 --- pacman-lib/src/pacman/po/.cvsignore:1.1 Tue Jan 16 22:40:09 2007 +++ pacman-lib/src/pacman/po/.cvsignore Thu Feb 8 00:36:26 2007 @@ -4,3 +4,5 @@ POTFILES stamp-po +remove-potcdate.sin +remove-potcdate.sed Index: pacman-lib/src/pacman/po/remove-potcdate.sin diff -u /dev/null pacman-lib/src/pacman/po/remove-potcdate.sin:1.1 --- /dev/null Thu Feb 8 00:36:26 2007 +++ pacman-lib/src/pacman/po/remove-potcdate.sin Thu Feb 8 00:36:26 2007 @@ -0,0 +1,19 @@ +# Sed script that remove the POT-Creation-Date line in the header entry +# from a POT file. +# +# The distinction between the first and the following occurrences of the +# pattern is achieved by looking at the hold space. +/^"POT-Creation-Date: .*"$/{ +x +# Test if the hold space is empty. +s/P/P/ +ta +# Yes it was empty. First occurrence. Remove the line. +g +d +bb +:a +# The hold space was nonempty. Following occurrences. Do nothing. +x +:b +}

1 0

[pacman-dev] Blocked commits
by Aaron Griffin 08 Feb '07

08 Feb '07

>From the admin queue (messages too big) - i need to automate this at some point. Date: Wednesday, February 7, 2007 @ 17:29:22 Author: dan Path: /home/cvs-pacman/pacman-lib Modified: Makefile.am (1.9 -> 1.10) configure.ac (1.28 -> 1.29) doc/Makefile.am (1.11 -> 1.12) doc/libalpm.3 (1.2 -> 1.3) doc/makepkg.8 (1.2 -> 1.3) doc/pacman.8 (1.2 -> 1.3) Removed: doc/addendum.8.hu (1.1) doc/hu/.cvsignore (1.1) doc/hu/Makefile.am (1.3) doc/libalpm.3.in (1.2) doc/makepkg.8.in (1.5) doc/pacman.8.in (1.10) doc/po/.cvsignore (1.1) doc/po/hu.po (1.6) doc/po/pacman.pot (1.6) doc/po4a.cfg (1.3) Greatly simplify the way our non-existant translated manpages were being made. Ripped out all the po4a stuff, letting us cut down on yet another makedepends. Also moved all of the manpages to non-.in names. =============================================================== Date: Thursday, February 8, 2007 @ 00:24:18 Author: dan Path: /home/cvs-pacman/pacman-lib Added: doc/pacman.conf.5 (1.1) Modified: TODO.dan (1.5 -> 1.6) doc/PKGBUILD.5 (1.2 -> 1.3) doc/makepkg.8 (1.3 -> 1.4) doc/pacman.8 (1.3 -> 1.4) scripts/makepkg (1.45 -> 1.46) src/pacman/pacman.c (1.88 -> 1.89) * Nice overhaul of manpages. It is at least a start. * Alphabetized options in pacman usage.

1 0

[pacman-dev] CVS update of pacman-lib (7 files)
by dan＠archlinux.org 08 Feb '07

08 Feb '07

Date: Thursday, February 8, 2007 @ 00:24:18 Author: dan Path: /home/cvs-pacman/pacman-lib Added: doc/pacman.conf.5 (1.1) Modified: TODO.dan (1.5 -> 1.6) doc/PKGBUILD.5 (1.2 -> 1.3) doc/makepkg.8 (1.3 -> 1.4) doc/pacman.8 (1.3 -> 1.4) scripts/makepkg (1.45 -> 1.46) src/pacman/pacman.c (1.88 -> 1.89) * Nice overhaul of manpages. It is at least a start. * Alphabetized options in pacman usage. ---------------------+ TODO.dan | 10 doc/PKGBUILD.5 | 40 +-- doc/makepkg.8 | 572 +++++++++++--------------------------------------- doc/pacman.8 | 490 ++++++++++++++++++------------------------ doc/pacman.conf.5 | 137 +++++++++++ scripts/makepkg | 2 src/pacman/pacman.c | 4 7 files changed, 506 insertions(+), 749 deletions(-) Index: pacman-lib/TODO.dan diff -u pacman-lib/TODO.dan:1.5 pacman-lib/TODO.dan:1.6 --- pacman-lib/TODO.dan:1.5 Wed Feb 7 17:08:37 2007 +++ pacman-lib/TODO.dan Thu Feb 8 00:24:17 2007 @@ -62,8 +62,8 @@ needs to be in config.h and what does not. There may be excess #depends which are hard coded into the sources. (from TODO.autoconf) -Quick hits: -=========== +Other ideas: +============ unsigned int vs. unsigned- determine a standard and stick with it @@ -88,4 +88,8 @@ autogen.sh / autoclean.sh - these seem messy. Can we clean this up? - +Refine makepkg error codes. Each kind of failure could have its own code: + --package already built + --failed integ checks + --failed build + --etc. Index: pacman-lib/doc/PKGBUILD.5 diff -u pacman-lib/doc/PKGBUILD.5:1.2 pacman-lib/doc/PKGBUILD.5:1.3 --- pacman-lib/doc/PKGBUILD.5:1.2 Tue Feb 6 13:45:32 2007 +++ pacman-lib/doc/PKGBUILD.5 Thu Feb 8 00:24:18 2007 @@ -2,31 +2,32 @@ .ds DS Arch Linux .ds PB PKGBUILD .ds VR 3.0.0 -.TH PKGBUILD 5 "Feb 06, 2007" "PKGBUILD version \*(VR" "\*(DS Files" +.TH \*(PB 5 "Feb 07, 2007" "\*(PB version \*(VR" "\*(DS Files" .SH NAME -PKGBUILD \- \*(DS package build description file +\*(PB \- \*(DS package build description file + .SH DESCRIPTION -This manual page is meant to describe general rules about PKGBUILDs. Once -a PKGBUILD is written, the actual package is built using \fBmakepkg\fR and +This manual page is meant to describe general rules about \*(PBs. Once +a \*(PB is written, the actual package is built using \fBmakepkg\fR and installed with \fBpacman\fR. \fBNOTE:\fR If you have a local copy of the Arch Build System (ABS) tree -on your computer, you can copy the PKGBUILD.proto file to your new package +on your computer, you can copy the \*(PB.proto file to your new package build directory and edit it from there. To acquire/sync the ABS tree, use the \fBabs\fR script included with pacman/makepkg. -.SS Quick PKGBUILD Explanation -For an example of a PKGBUILD, see the \fBEXAMPLE\fR section. +.SS Quick \*(PB Explanation +For an example of a \*(PB, see the \fBEXAMPLE\fR section. \fIpkgname\fR defines the package name. It should not contain any uppercase letters. \fIpkgversion\fR defines the actual package version as given by the developers of the package. No dashes are allowed. \fIpkgrel\fR allows for -\*(DS-specific changes to the package or corrections to a PKGBUILD +\*(DS-specific changes to the package or corrections to a \*(PB without an upstream version change. The value should be an integer. \fIpkgdesc\fR is a short one-line description for the package, usually taken from the project's homepage or manpage. It is preferable to keep the length to one line for displaying during searches. These four variables are required in -every PKGBUILD. \fIurl\fR is also highly recommended so users can find more +every \*(PB. \fIurl\fR is also highly recommended so users can find more information on the package if needed. \fIdepends\fR and \fImakedepends\fR are bash arrays which define the @@ -49,7 +50,7 @@ $startdir/pkg). However, some customizations are often needed during the build process. -Once your PKGBUILD is created, you can run \fBmakepkg\fR from the build +Once your \*(PB is created, you can run \fBmakepkg\fR from the build directory. \fBmakepkg\fR will check dependencies and look for the source files required to build. If some are missing it will attempt to download them, provided there is a fully-qualified URL in the \fIsource()\fR array. @@ -100,14 +101,14 @@ .TP .B install Specifies a special install script that is to be included in the package. -This file should reside in the same directory as the PKGBUILD, and will be +This file should reside in the same directory as the \*(PB, and will be copied into the package by makepkg. It does not need to be included in the \fIsource\fR array. (eg, install=pkgname.install) .TP .B source \fI(array)\fR The \fIsource\fR line is an array of source files required to build the -package. Source files must reside in the same directory as the PKGBUILD +package. Source files must reside in the same directory as the \*(PB file, unless they have a fully-qualified URL. .TP @@ -122,8 +123,8 @@ If this field is present, it should contain an MD5 hash for every source file specified in the \fIsource\fR array (in the same order). \fImakepkg\fR will use this to verify source file integrity during subsequent builds. To easily -generate md5sums, first build using the PKGBUILD then run -\fBmakepkg -g >>PKGBUILD\fR. Then you can edit the PKGBUILD and move the +generate md5sums, first build using the \*(PB then run +\fBmakepkg -g >>\*(PB\fR. Then you can edit the \*(PB and move the \fImd5sums\fR line from the bottom to an appropriate location. \fBNOTE:\fR makepkg supports multiple integrity algorithms and their corresponding arrays (i.e. sha1sums for the SHA1 algorithm), however official @@ -221,7 +222,7 @@ .P To use this feature, just create a file (eg, pkgname.install) and put it in -the same directory as the PKGBUILD script. Then use the \fIinstall\fR +the same directory as the \*(PB script. Then use the \fIinstall\fR directive: install=pkgname.install @@ -230,7 +231,7 @@ A template install file is available in your ABS tree (/var/abs/install.proto). .SH EXAMPLE -The following is an example PKGBUILD for the 'modutils' package. For more +The following is an example \*(PB for the 'modutils' package. For more examples, look through the ABS tree. .nf @@ -265,17 +266,18 @@ .SH SEE ALSO .BR makepkg (8), -.BR makepkg.conf (5), .BR pacman (8) -.BR pacman.conf (5) See the Arch Linux website at <http://www.archlinux.org> for more current -information on the distribution, and +information on the distribution and the \fBpacman\fP family of tools, and <http://wiki.archlinux.org/index.php/Arch_Packaging_Standards> for recommendations on packaging standards. + .SH AUTHORS +.nf Judd Vinet <jvinet(a)zeroflux.org> Aurelien Foret <aurelien(a)archlinux.org> Aaron Griffin <aaron(a)archlinux.org> Dan McGee <dan(a)archlinux.org> See the 'AUTHORS' file for additional contributors. +.fi Index: pacman-lib/doc/makepkg.8 diff -u pacman-lib/doc/makepkg.8:1.3 pacman-lib/doc/makepkg.8:1.4 --- pacman-lib/doc/makepkg.8:1.3 Wed Feb 7 17:29:21 2007 +++ pacman-lib/doc/makepkg.8 Thu Feb 8 00:24:18 2007 @@ -1,455 +1,145 @@ -.TH makepkg 8 "January 30, 2006" "makepkg #VERSION#" "" +." the string declarations are a start to try and make distro independent +.ds DS Arch Linux +.ds PB PKGBUILD +.ds VR 3.0.0 +.TH makepkg 8 "Feb 07, 2007" "makepkg version \*(VR" "\*(DS Utilities" .SH NAME makepkg \- package build utility -.SH SYNOPSIS -\fBmakepkg [options]\fP -.SH DESCRIPTION -\fBmakepkg\fP will build packages for you. All it needs is -a build-capable linux platform, wget, and some build scripts. The advantage -to a script-based build is that you only really do the work once. Once you -have the build script for a package, you just need to run makepkg and it -will do the rest: download and validate source files, check dependencies, -configure the buildtime 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. -.SH BUILD PROCESS (or How To Build Your Own Packages) -Start in an isolated directory (ie, it's not used for anything other -than building this package). The build script should be called PKGBUILD -and it should bear resemblance to the example below. - -\fBNOTE:\fP If you have a local copy of the Arch Build System (ABS) tree -on your computer, you can copy the PKGBUILD.proto file to your new package -build directory and edit it from there. To acquire/sync the ABS tree, use -the \fBabs\fP script included with pacman/makepkg. - -.TP -.TP -.SH PKGBUILD Example: -.RS -.nf -pkgname=modutils -pkgver=2.4.25 -pkgrel=1 -pkgdesc="Utilities for inserting and removing modules from the linux kernel" -url="http://www.kernel.org" -backup=(etc/modules.conf) -makedepends=('bash' 'mawk') -depends=('glibc' 'zlib') -source=(ftp://ftp.kernel.org/pub/linux/utils/kernel/$pkgname/v2.4/$pkgname-$pkgver.tar.bz2 \\ - modules.conf) -md5sums=('2c0cca3ef6330a187c6ef4fe41ecaa4d' \\ - '35175bee593a7cc7d6205584a94d8625') - -build() { - cd $startdir/src/$pkgname-$pkgver - ./configure --prefix=/usr --enable-insmod-static - make || return 1 - make prefix=$startdir/pkg/usr install - mv $startdir/pkg/usr/sbin $startdir/pkg - mkdir -p $startdir/pkg/etc - cp ../modules.conf $startdir/pkg/etc -} -.fi -.RE - -As you can see, the setup is fairly simple. The first three lines define -the package name and version info. They also define the final package name -which will be of the form \fI$pkgname-$pkgver-$pkgrel.pkg.tar.gz\fP. The fourth -line provides a brief description of the package. These four lines should -be present in every PKGBUILD script. - -The line with \fIbackup=\fP specifies files that should be treated specially -when removing or upgrading packages. See \fBHANDLING CONFIG FILES\fP in -the \fIpacman\fP manpage for more information on this. - -Lines 7 and 8 list the dependencies for this package. The \fIdepends\fP array -specifies the run-time dependencies and \fImakedepends\fP specifies the build-time -dependencies. In order to run the package, \fIdepends\fP must be satisfied. To -build the package, \fBall\fP dependencies must be satisifed first. makepkg -will check this before attempting to build the package. - -The \fIsource\fP array tells makepkg which files to download/extract before compiling -begins. The \fImd5sums\fP array provides md5sums for each of these files. These -are used to validate the integrity of the source files. - -Once your PKGBUILD is created, you can run \fImakepkg\fP from the build directory. -makepkg will then check dependencies and look for the source files required to -build. If some are missing it will attempt to download them, provided there is -a fully-qualified URL in the \fIsource\fP array. - -The sources are then extracted into a directory called ./src and -the \fIbuild\fP function is called. This is where all package configuration, -building, and installing should be done. Any customization will likely take -place here. - -After a package is built, the \fIbuild\fP function must install the package -files into a special package root, which can be referenced by \fB$startdir/pkg\fP -in the \fIbuild\fP function. The typical way to do this is one of the following: -.RS -.nf - -make DESTDIR=$startdir/pkg install - -or - -make prefix=$startdir/pkg/usr install - -.fi -.RE -Notice that the "/usr" portion should be present with "prefix", but not "DESTDIR". -"DESTDIR" is the favorable option to use, but not all Makefiles support it. Use -"prefix" only when "DESTDIR" is unavailable. - -Once the package is successfully installed into the package root, \fImakepkg\fP -will remove some directories (as per Arch Linux package guidelines; if you use -this elsewhere, feel free to change it) like /usr/doc and /usr/info. It will -then strip debugging info from libraries and binaries and generate a meta-info -file. Finally, it will compress everything into a .pkg.tar.gz file and leave it -in the directory you ran \fBmakepkg\fP from. - -At this point you should have a package file in the current directory, named -something like name-version-release.pkg.tar.gz. Done! - -.SH Install/Upgrade/Remove Scripting -Pacman has the ability to store and execute a package-specific script when it -installs, removes, or upgrades a package. This allows a package to "configure -itself" after installation and do the opposite right before it is removed. - -The exact time the script is run varies with each operation: -.TP -.B pre_install -script is run right before files are extracted. - -.TP -.B post_install -script is run right after files are extracted. - -.TP -.B pre_upgrade -script is run right before files are extracted. - -.TP -.B post_upgrade -script is run after files are extracted. - -.TP -.B pre_remove -script is run right before files are removed. - -.TP -.B post_remove -script is run right after files are removed. - -.RE -To use this feature, just create a file (eg, pkgname.install) and put it in -the same directory as the PKGBUILD script. Then use the \fIinstall\fP directive: -.RS -.nf -install=pkgname.install -.fi -.RE - -The install script does not need to be specified in the \fIsource\fP array. - -.TP -.TP -.SH Install scripts must follow this format: -.RS -.nf -# arg 1: the new package version -pre_install() { - # - # do pre-install stuff here - # - /bin/true -} - -# arg 1: the new package version -post_install() { - # - # do post-install stuff here - # - /bin/true -} -# arg 1: the new package version -# arg 2: the old package version -pre_upgrade() { - # - # do pre-upgrade stuff here - # - /bin/true -} - -# arg 1: the new package version -# arg 2: the old package version -post_upgrade() { - # - # do post-upgrade stuff here - # - /bin/true -} - -# arg 1: the old package version -pre_remove() { - # - # do pre-remove stuff here - # - /bin/true -} - -# arg 1: the old package version -post_remove() { - # - # do post-remove stuff here - # - /bin/true -} - -op=$1 -shift -$op $* -.fi -.RE - -This template is also available in your ABS tree (/var/abs/install.proto). - -.SH PKGBUILD Directives -.TP -.B pkgname -The name of the package. This has be a unix-friendly name as it will be -used in the package filename. - -.TP -.B pkgver -This is the version of the software as released from the author (eg, 2.7.1). - -.TP -.B pkgrel -This is the release number specific to Arch Linux packages. - -.TP -.B pkgdesc -This should be a brief description of the package and its functionality. - -.TP -.B options -This array allows you to override some of makepkg's default behaviour -when building packages. To set an option, just include the option name -in the \fBoptions\fP array. -.TP -.RS -\fIAvailable Options:\fP -.RS -.TP -.B FORCE -force the package to be upgraded by \fB--sysupgrade\fP, even -if its an older version. -.TP -.B KEEPDOCS -do not remove /usr/share/doc and /usr/share/info directories. -.TP -.B NOSTRIP -do not strip debugging symbols from binaries and libraries. -.RE -.RE - -.TP -.B url -This field contains an optional URL that is associated with the piece of software -being packaged. This is typically the project's website. - -.TP -.B license -This field specifies the license(s) that apply to the package. Commonly-used -licenses are typically found in \fI/usr/share/licenses/common\fP. If you -see the package's license there, simply reference it in the license field -(eg, \fBlicense="GPL"\fP). If the package provides a license not found in -\fI/usr/share/licenses/common\fP, then you should include the license in -the package itself and set \fBlicense="custom"\fP or \fBlicense="custom:LicenseName"\fP. -The license itself should be placed in a directory called -\fI$startdir/pkg/usr/share/licenses/$pkgname\fP. -.TP -.RE -If multiple licenses are applied, use the array form: \fBlicense=('GPL' 'FDL')\fP - -.TP -.B install -Specifies a special install script that is to be included in the package. -This file should reside in the same directory as the PKGBUILD, and will be -copied into the package by makepkg. It does not need to be included in the -\fIsource\fP array. (eg, install=modutils.install) - -.TP -.B source \fI(array)\fP -The \fIsource\fP line is an array of source files required to build the -package. Source files must reside in the same directory as the PKGBUILD -file, unless they have a fully-qualified URL. Then if the source file -does not already exist in /var/cache/pacman/src, the file is downloaded -by wget. - -.TP -.B md5sums \fI(array)\fP -If this field is present, it should contain an MD5 hash for every source file -specified in the \fIsource\fP array (in the same order). makepkg will use -this to verify source file integrity during subsequent builds. To easily -generate md5sums, first build using the PKGBUILD then run -\fBmakepkg -g >>PKGBUILD\fP. Then you can edit the PKGBUILD and move the -\fImd5sums\fP line from the bottom to an appropriate location. - -.TP -.B groups \fI(array)\fP -This is an array of symbolic names that represent groups of packages, allowing -you to install multiple packages by requesting a single target. For example, -one could install all KDE packages by installing the 'kde' group. - -.TP -.B backup \fI(array)\fP -A space-delimited array of filenames (without a preceding slash). The -\fIbackup\fP line will be propagated to the package meta-info file for -pacman. This will designate all files listed there to be backed up if this -package is ever removed from a system. See \fBHANDLING CONFIG FILES\fP in -the \fIpacman\fP manpage for more information. - -.TP -.B depends \fI(array)\fP -An array of packages that this package depends on to build and run. Packages -in this list should be surrounded with single quotes and contain at least the -package name. They can also include a version requirement of the form -\fBname<>version\fP, where <> is one of these three comparisons: \fB>=\fP -(greater than equal to), \fB<=\fP (less than or equal to), or \fB=\fP (equal to). -See the PKGBUILD example above for an example of the \fIdepends\fP directive. - -.TP -.B makedepends \fI(array)\fP -An array of packages that this package depends on to build (ie, not required -to run). Packages in this list should follow the same format as \fIdepends\fP. - -.TP -.B conflicts \fI(array)\fP -An array of packages that will conflict with this package (ie, they cannot both -be installed at the same time). This directive follows the same format as -\fIdepends\fP except you cannot specify versions here, only package names. - -.TP -.B provides \fI(array)\fP -An array of "virtual provisions" that this package provides. This allows a package -to provide dependency names other than it's own package name. For example, the -kernel-scsi and kernel-ide packages can each provide 'kernel' which allows packages -to simply depend on 'kernel' rather than "kernel-scsi OR kernel-ide OR ..." - -.TP -.B replaces \fI(array)\fP -This is an array of packages that this package should replace, and can be used to handle -renamed/combined packages. For example, if the kernel package gets renamed -to kernel-ide, then subsequent 'pacman -Syu' calls will not pick up the upgrade, due -to the differing package names. \fIreplaces\fP handles this. +.SH SYNOPSIS +.B makepkg +[\fIoptions\fR] -.SH MAKEPKG OPTIONS -.TP -.B "\-b, \-\-builddeps" -Build missing dependencies from source. When makepkg finds missing build-time or -run-time dependencies, it will look for the dependencies' PKGBUILD files under -$ABSROOT (set in your /etc/makepkg.conf). If it finds them it will -run another copy of makepkg to build and install the missing dependencies. -The child makepkg calls will be made with the \fB-b\fP and \fB-i\fP options. -.TP -.B "\-B, \-\-noccache" -Do not use ccache during build. -.TP -.B "\-c, \-\-clean" -Clean up leftover work files/directories after a successful build. -.TP -.B "\-C, \-\-cleancache" -Removes all source files from the cache directory to free up diskspace. -.TP -.B "\-d, \-\-nodeps" -Do not perform any dependency checks. This will let you override/ignore any -dependencies required. There's a good chance this option will break the build -process if all of the dependencies aren't installed. -.TP -.B "\-e, \-\-noextract" -Do not extract source files. Instead, use whatever already exists in the -src/ directory. This is handy if you want to go into src and manually -patch/tweak code, then make a package out of the result. -.TP -.B "\-f, \-\-force" -\fBmakepkg\fP will not build a package if a \fIpkgname-pkgver-pkgrel.pkg.tar.gz\fP -file already exists in the build directory. You can override this behaviour with -the \fB--force\fP switch. -.TP -.B "\-g, \-\-genmd5" -Download all source files (if required) and use \fImd5sum\fP to generate md5 hashes -for each of them. You can then redirect the output into your PKGBUILD for source -validation (makepkg -g >>PKGBUILD). -.TP -.B "\-h, \-\-help" -Output syntax and commandline options. -.TP -.B "\-i, \-\-install" -Install/Upgrade the package after a successful build. -.TP -.B "\-j <jobs>" -Sets MAKEFLAGS="-j<jobs>" before building the package. This is useful for overriding -the MAKEFLAGS setting in /etc/makepkg.conf. -.TP -.B "\-m, \-\-nocolor" -Disable color in output messages -.TP -.B "\-n, \-\-nostrip" -Do not strip binaries and libraries. -.TP -.B "\-o, \-\-nobuild" -Download and extract files only, do not build. -.TP -.B "\-p <buildscript>" -Read the package script \fI<buildscript>\fP instead of the default (\fIPKGBUILD\fP). -.TP -.B "\-r, \-\-rmdeps" -Upon successful build, remove any dependencies installed by makepkg/pacman during -dependency auto-resolution (using \fB-b\fP or \fB-s\fP). -.TP -.B "\-s, \-\-syncdeps" -Install missing dependencies using pacman. When makepkg finds missing build-time -or run-time dependencies, it will run pacman to try and resolve them. If successful, -pacman will download the missing packages from a package repository and -install them for you. -.TP -.B "\-S, \-\-sudosync" -Install missing dependencies using pacman and sudo. This is the same as \fB-s\fP -except that makepkg will call pacman with sudo. This means you don't have to +.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. + +\fBmakeworld\fP can be used to rebuild an entire package group or the entire +build tree. See \fBmakeworld --help\fP for syntax. + +.SH OPTIONS +.TP +.B \-b, --builddeps +Build missing dependencies from source. When \fBmakepkg\fP finds missing +build-time or run-time dependencies, it will look for the dependencies' +\fB\*(PB\fP files under \fIABSROOT\fP (set in \fBmakepkg.conf\fP). If it finds +them it will call \fBmakepkg\fP to build and install the missing dependencies. +The child calls will be made with the \fB-b\fP and \fB-i\fP options. +.TP +.B \-B, --noccache +Disable the use of \fBccache\fP during build (useful for select packages that +have problems with \fBccache\fP). +.TP +.B \-c, --clean +Clean up leftover work files and directories after a successful build. +.TP +.B \-C, --cleancache +Removes all cached source files from the directory specified in \fISRCDEST\fP +in \fBmakepkg.conf\fP. +.TP +.B \-d, --nodeps +Do not perform any dependency checks. This will let you override and ignore any +dependencies required. There is a good chance this option will break the build +process if all of the dependencies are not installed. +.TP +.B \-e, --noextract +Do not extract source files; use whatever source already exists in the src/ +directory. This is handy if you want to go into src and manually patch or tweak +code, then make a package out of the result. Keep in mind that creating a patch +may be a better solution to allow others to use your \fB\*(PB\fP. +.TP +.B \-f, --force +\fBmakepkg\fP will not build a package if a built package already exists in the +\fIPKGDEST\fP (set in \fBmakepkg.conf\fP) directory, which may default to the +current directory. This allows the built package to be overwritten. +.TP +.B \-g, --geninteg +For each source file in the source array of \fB\*(PB\fP, download the file if +required and generate integrity checks. The integrity checks generated are +determined by the value of the \fIINTEGRITY_CHECK\fP array in makepkg.conf. +This output can be redirected into your \fB\*(PB\fP for source validation +(makepkg -g >> \*(PB). +.TP +.B \-h, --help +Output syntax and command line options. +.TP +.B \-i, --install +Install or upgrade the package after a successful build using \fBpacman\fP. +.TP +.B \-j \fIjobs\fP +Sets MAKEFLAGS="-j\fIjobs\fP" before building the package. This is useful for +overriding the \fIMAKEFLAGS\fP setting in \fBmakepkg.conf\fP. +.TP +.B \-m, --nocolor +Disable color in output messages. +.TP +.B \-o, --nobuild +Download and extract files only, but do not build them. Useful with the +\fB--noextract\fP option if you wish to tweak the files in src/ before +building. +.TP +.B \-p \fIbuildscript\fP +Read the package script \fIbuildscript\fP instead of the default, \fI\*(PB\fP. +.TP +.B \-r, --rmdeps +Upon successful build, remove any dependencies installed by \fBmakepkg\fP +during dependency auto-resolution (using \fB-b\fP or \fB-s\fP). +.TP +.B \-R, --repackage +Repackage contents of pkg/ without rebuilding the package. This is useful if +you forgot a depend or install file in your \fB\*(PB\fP and the build itself +will not change. +.TP +.B \-s, --syncdeps +Install missing dependencies using \fBpacman\fP. When missing build-time or +run-time dependencies are found, \fBpacman\fP will try to resolve them. If +successful, the missing packages will be downloaded and installed. +.TP +.B \-S, --sudosync +Install missing dependencies using \fBpacman\fP and \fBsudo\fP. This is the +same as \fB-s\fP except that \fBsudo\fP is used, meaning you do not have to build as root to use dependency auto-resolution. .TP -.B "\-w <destdir>" -Write the resulting package file to the directory \fI<destdir>\fP instead of the -current working directory. -.TP -.B "\-\-noconfirm" -When calling pacman to resolve dependencies or conflicts, makepkg can pass -the \fI--noconfirm\fP option to it so it does not wait for any user -input before proceeding with operations. -.TP -.B "\-\-noprogressbar" -When calling pacman, makepkg can pass the \fI--noprogressbar\fP option to it. -This is useful if one is directing makepkg's output to a non-terminal (ie, a file). +.B \--noconfirm +(Passed to \fBpacman\fP) Prevent \fBpacman\fP from waiting for user input +before proceeding with operations. +.TP +.B \--noprogressbar +(Passed to \fBpacman\fP) Prevent \fBpacman\fP from displaying a progress bar; +useful if you are redirecting makepkg output to file. .SH CONFIGURATION -Configuration options are stored in \fI/etc/makepkg.conf\fP. This file is parsed -as a bash script, so you can export any special compiler flags you wish -to use. This is helpful for building for different architectures, or with -different optimizations. +Configuration options are stored in \fBmakepkg.conf\fP. This file is sourced, +so you can include any special compiler flags you wish to use. This is helpful +for building for different architectures, or with different optimizations. + +\fBNOTE:\fP This does not guarantee that all package Makefiles will use your +exported variables. Some of them are non-standard... + +The file is fairly well commented, so follow directions given there for +customization. -\fBNOTE:\fP This does not guarantee that all package Makefiles will use -your exported variables. Some of them are flaky... .SH SEE ALSO -\fBpacman\fP is the package manager that uses packages built by makepkg. +.BR makepkg.conf (5), +.BR \*(PB (5), +.BR pacman (8) + +See the Arch Linux website at <http://www.archlinux.org> for more current +information on the distribution and the \fBpacman\fP family of tools, and +<http://wiki.archlinux.org/index.php/Arch_Packaging_Standards> for +recommendations on packaging standards. -See the Arch Linux Documentation for package-building guidelines if you wish -to contribute packages to the Arch Linux project. -.SH AUTHOR +.SH AUTHORS .nf Judd Vinet <jvinet(a)zeroflux.org> +Aurelien Foret <aurelien(a)archlinux.org> +Aaron Griffin <aaron(a)archlinux.org> +Dan McGee <dan(a)archlinux.org> +See the 'AUTHORS' file for additional contributors. .fi Index: pacman-lib/doc/pacman.8 diff -u pacman-lib/doc/pacman.8:1.3 pacman-lib/doc/pacman.8:1.4 --- pacman-lib/doc/pacman.8:1.3 Wed Feb 7 17:29:21 2007 +++ pacman-lib/doc/pacman.8 Thu Feb 8 00:24:18 2007 @@ -1,334 +1,258 @@ -.TH pacman 8 "January 21, 2006" "pacman @PACKAGE_VERSION@" "" +." the string declarations are a start to try and make distro independent +.ds DS Arch Linux +.ds PB PKGBUILD +.ds VR 3.0.0 +.TH pacman 8 "Feb 07, 2007" "pacman version \*(VR" "\*(DS Utilities" .SH NAME pacman \- package manager utility + .SH SYNOPSIS -\fBpacman <operation> [options] <package> [package] ...\fP +.B pacman +<\fIoperation\fR> [\fIoptions\fR] [\fIpackages\fR] + .SH DESCRIPTION \fBpacman\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 package are \fIgzipped tar\fP format. +packages on a Linux system. It has dependency support, package groups, install +and uninstall hooks, and the ability to sync your local machine with a remote +ftp server to automatically upgrade packages. \fBpacman\fP packages are a +zipped tar 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 .tar.gz packages. See -\fBQUERY OPTIONS\fP below. -.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 -S qt\fP will download -qt and all the packages it depends on and install them. You could also use -\fBpacman -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 takes care of config files. +.B \-A, --add (deprecated) +Add a package to the system. Package will be uncompressed into the installation +root and the database will be updated. The package will not be installed if +another version is already installed. Please use \fB--upgrade\fP in place of +this option. +.TP +.B \-F, --freshen +This is like \fB--upgrade\fP except it will only upgrade packages already +installed on the 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 .tar.gz +packages. See \fBQUERY OPTIONS\fP below. +.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 +is used. See \fBREMOVE OPTIONS\fP below. +.TP +.B \-S, --sync +Synchronize packages. Packages are installed directly from the ftp servers, +complete with all dependencies required to run the packages. For example, +\fBpacman -S qt\fP will download and install \fBqt\fP and all the packages it +depends on. You can also use \fBpacman -Su\fP to upgrade all packages that are +out of date. See \fBSYNC OPTIONS\fP below. +.TP +.B \-U, --upgrade +Upgrade or add a package to the system. This is a "remove-then-add" process. +See \fBHANDLING CONFIG FILES\fP for an explanation on how pacman takes care of +config files. .TP -.B "\-V, \-\-version" +.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. +.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 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. +.B \-d, --nodeps +Skips all dependency checks. Normally, pacman will always check a package's +dependency fields to ensure that all dependencies are installed and there are +no package conflicts in the system. +.TP +.B \-f, --force +Bypass file conflict checks and overwrite 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 \fIpath\fP +Specify alternative installation root (default is "/"). However, this should +\fInot\fP be used as a way to install software into /usr/local instead of /usr, +for example. This option 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. +.B \-v, --verbose +Output more status messages, such as the Root and DBPath. .TP -.B "\-\-config <path>" +.B \--config \fIfilepath\fP 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 +.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 from a script. .TP -.B "\-\-noprogressbar" -Do not show a progress bar when downloading files. This can be useful for +.B \--noprogressbar +Do not show a progress bar when downloading files. This can be useful for scripts that call pacman and capture the output. -.SH SYNC OPTIONS + +.SH QUERY OPTIONS .TP -.B "\-c, \-\-clean" -Remove old packages from the cache. When pacman 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 "\-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. +.B \-e, --orphans +List all packages that were pulled in by a previously installed package but no +longer required by any installed package. .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. +.B \-g, --groups +Display all package members of a named group, or all grouped packages if +no name is specified. .TP -.B "\-s, \-\-search <regexp>" -This will search each package in the package list for names or descriptions -that matches <regexp>. -.TP -.B "\-u, \-\-sysupgrade" -Upgrades all packages that are out of date. pacman will examine every -package installed on the system, and if a newer package exists on the -server it will upgrade. pacman 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. +.B \-i, --info +Display information on a given package. The \fB-p\fP option can be used if +querying a package file instead of the local database. .TP -.B "\-w, \-\-downloadonly" -Retrieve all packages from the server, but do not install/upgrade anything. +.B \-l, --list +List all files owned by a given package. Multiple packages can be specified on +the command line. .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 +.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 \fB--upgrade\fP. .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 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 +.B \-o, --owns \fIfile\fP +Search for the package that owns \fIfile\fP. .TP -.B "\-e, \-\-orphans" -List all packages that were explicitly installed (ie, not pulled in -as a dependency by other packages) and are not required by any other -packages. +.B \-p, --file +Signifies that the package supplied on the command line is a file and not an +entry in the database. The file will be decompressed and queried. This is +useful with \fB--info\fP and \fB--list\fP. +.TP +.B \-s, --search \fIregexp\fP +This will search each locally-installed package for names or descriptions that +matche \fIregexp\fP. .TP -.B "\-g, \-\-groups" -Display all package members of a named group, or all grouped packages if -no name is specified. +.B \-u, --upgrades +Lists all packages that are out of date on the local system. This option works best if the sync database is refreshed using \fB-Sy\fP. + +.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 to ignore file backup designations. Normally, when a file is +removed from the system the database is checked to see if the file should be +renamed with a .pacsave extension. +.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 analogous to a backwards \fB--sync\fP +operation. + +.SH SYNC OPTIONS .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. +.B \-c, --clean +Remove old packages from the cache to free up disk space. When \fBpacman\fP +downloads packages, it saves them in \fI/var/cache/pacman/pkg\fP. Use one +\fB--clean\fP switch to remove \fIold\fP packages; use two to remove \fIall\fP +packages from the cache. +.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 and other information for a given package. This will search +through all repositories for a matching package. +.TP +.B \-l, --list +List all packages in the specified repositories. Multiple repositories can be +specified on the command line. .TP -.B "\-l, \-\-list" -List all files owned by <package>. Multiple packages can be specified on -the command line. +.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 "\-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. +.B \-s, --search \fIregexp\fP +This will search each package in the sync databases for names or descriptions +that match \fIregexp\fP. +.TP +.B \-u, --sysupgrade +Upgrades all packages that are out of date. Each currently-installed package +will be examined and upgraded if a newer package exists. A report of all +packages to upgrade will be presented and the operation will not proceed +without user confirmation. Dependencies are automatically resolved at this +level and will be installed/upgraded if necessary. .TP -.B "\-o, \-\-owns <file>" -Search for the package that owns <file>. +.B \-w, --downloadonly +Retrieve all packages from the server, but do not install/upgrade anything. .TP -.B "\-p, \-\-file" -Tells pacman 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 matches <regexp>. +.B \-y, --refresh +Download a fresh copy of the master package list from the server(s) defined in +\fBpacman.conf\fP. This should typically be used each time you use +\fB--sysupgrade\fP. +.TP +.B \--ignore \fIpackage\fP +Directs \fBpacman\fP to ignore upgrades of \fIpackage\fP even if there is one +available. + .SH HANDLING CONFIG FILES -pacman 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: +pacman uses the same logic as rpm to determine action against files that are +designated to be backed up. During an upgrade, 3 md5 hashes are used 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. +All three files are the same, so overwrites are not an issue 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. +The current file is the same as the original but the new one differs. Since +the user did not ever modify the file, and the new one may contain improvements +or bugfixes, 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. +Both package versions contain the exact same file, but the one on the +filesystem has been modified. 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. +The new file is identical to the current file. 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 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/passwd etc/group etc/shadow -NoUpgrade = etc/fstab +All three files are different, so install the new file with a .pacnew extension +and warn the user. The user must then manually merge any necessary changes into +the original file. -Include = /etc/pacman.d/current +.SH CONFIGURATION +See +.BR pacman.conf (5) +for more details on configuring pacman using the \fBpacman.conf\fP file. -[custom] -Server = file:///home/pkgs +.SH BUGS +Bugs? You must be kidding, there are no bugs in this software. But if we happen +to be wrong, send us an email with as much detail as possible to +<pacman-dev(a)archlinux.org>. -.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. -.B "CacheDir = path/to/cache/dir" -Overrides the default location of the package cache directory. The default is -\fIvar/cache/pacman\fP. -.TP -.TP -.B "HoldPkg = <package> [package] ..." -If a user tries to \fB--remove\fP a package that's listed in HoldPkg, pacman -will ask for confirmation before proceeding. -.TP -.B "IgnorePkg = <package> [package] ..." -Instructs pacman to ignore any upgrades for this package when performing a -\fB--sysupgrade\fP. -.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 will use this proxy server for all ftp/http transfers. -.TP -.B "XferCommand = /path/to/command %u" -If set, pacman 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'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 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.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. -The order of repositories in the file matters; repositories listed first will -take precidence over those listed later in the file when packages in two -repositories have identical names, regardless of version number. -.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/var/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. +.SH SEE ALSO +.BR pacman.conf (5), +.BR makepkg (8), +.BR libalpm (3) -.RS -.nf -# gensync /var/abs/local /home/pkgs/custom.db.tar.gz -.fi -.RE +See the Arch Linux website at <http://www.archlinux.org> for more current +information on the distribution and the \fBpacman\fP family of tools. -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 -\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 +.SH AUTHORS .nf Judd Vinet <jvinet(a)zeroflux.org> +Aurelien Foret <aurelien(a)archlinux.org> +Aaron Griffin <aaron(a)archlinux.org> +Dan McGee <dan(a)archlinux.org> +See the 'AUTHORS' file for additional contributors. .fi Index: pacman-lib/doc/pacman.conf.5 diff -u /dev/null pacman-lib/doc/pacman.conf.5:1.1 --- /dev/null Thu Feb 8 00:24:18 2007 +++ pacman-lib/doc/pacman.conf.5 Thu Feb 8 00:24:18 2007 @@ -0,0 +1,137 @@ +." the string declarations are a start to try and make distro independent +.ds DS Arch Linux +.ds PB PKGBUILD +.ds VR 3.0.0 +.TH \*(PB 5 "Feb 07, 2007" "pacman.conf version \*(VR" "\*(DS Files" +.SH NAME +pacman.conf \- pacman package manager configuration file + +.SH DESCRIPTION + +\fBpacman\fP will attempt to read \fBpacman.conf\fP each time it is invoked. +This configuration file is divided into sections or \fIrepositories\fP. Each +section defines a package repository that \fBpacman\fP can use when searching +for packages in \fB--sync\fP mode. The exception to this is the \fIoptions\fP +section, which defines global options. + +.SH EXAMPLE +.RS +.nf +# +# pacman.conf +# +[options] +NoUpgrade = etc/passwd etc/group etc/shadow +NoUpgrade = etc/fstab + +[current] +Include = /etc/pacman.d/current + +[custom] +Server = file:///home/pkgs +.fi +.RE + +.SH 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 = \fIpackage\fP ... +If a user tries to \fB--remove\fP a package that's listed in \fBHoldPkg\fI, +\fBpacman\fP will ask for confirmation before proceeding. +.TP +.B IgnorePkg = \fIpackage\fP ... +Instructs \fBpacman\fP to ignore any upgrades for this package when performing a +\fB--sysupgrade\fP. +.TP +.B Include = \fIpath\fP +Include another config file. This file can include repositories or general +configuration options. +.TP +.B ProxyServer = <\fIhost\fP|\fIip\fP>[:\fIport\fP] +If set, \fBpacman\fP will use this proxy server for all ftp/http transfers. +.TP +.B XferCommand = \fI/path/to/command %u\fP +If set, an external program will be used to download all remote files. All +instances of \fB%u\fP will be replaced with the download URL. 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 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 = \fIfile\fP ... +All files listed with a \fBNoUpgrade\fP directive will never be touched during +a package install/upgrade. Do \fInot\fP include the leading slash when +specifying files. +.TP +.B NoExtract = \fIfile\fP ... +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 +\fBapache\fP package. +.TP +.B UseSyslog +Log action messages through \fBsyslog()\fP. This will insert log entries into +\fI/var/log/messages\fP or equivalent. +.TP +.B LogFile = \fI/path/to/file\fP +Log actions directly to a file. Default is \fI/var/log/pacman.log\fP. + +.SH REPOSITORY SECTIONS +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 (the two above are 'current' and 'custom'). Locations are +defined with the \fBServer\fP directive and follow a URL naming structure. If +you want to use a local directory, you can specify the full path with +a 'file://' prefix, as shown above. + +The order of repositories in the file matters; repositories listed first will +take precedence over those listed later in the file when packages in two +repositories have identical names, regardless of version number. + +.SH USING YOUR OWN REPOSITORY +If you have numerous custom packages of your own, it is often easier to generate your own custom local repository than install them all with the \fB--upgrade\fP option. All you need to do is generate a compressed package database in the directory with these packages so \fBpacman\fP can find it when run with \fB--refresh\fP. + +.RS +.nf +repo-add /home/pkgs/custom.db.tar.gz /home/pkgs/*.pkg.tar.gz +.fi +.RE + +The above command will generate a compressed database named +\fI/home/pkgs/custom.db.tar.gz\fP. 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 \fBpacman\fP's --refresh option. + +For more information on the \fBrepo-add\fP command, use \fB repo-add --help\fP. + +.SH SEE ALSO +.BR pacman (8), +.BR libalpm (3) + +See the Arch Linux website at <http://www.archlinux.org> for more current +information on the distribution and the \fBpacman\fP family of tools. + +.SH AUTHORS +.nf +Judd Vinet <jvinet(a)zeroflux.org> +Aurelien Foret <aurelien(a)archlinux.org> +Aaron Griffin <aaron(a)archlinux.org> +Dan McGee <dan(a)archlinux.org> +See the 'AUTHORS' file for additional contributors. +.fi Index: pacman-lib/scripts/makepkg diff -u pacman-lib/scripts/makepkg:1.45 pacman-lib/scripts/makepkg:1.46 --- pacman-lib/scripts/makepkg:1.45 Tue Feb 6 17:36:14 2007 +++ pacman-lib/scripts/makepkg Thu Feb 8 00:24:18 2007 @@ -346,7 +346,7 @@ echo " -p <buildscript> Use an alternate build script (instead of '$BUILDSCRIPT')" echo " -r, --rmdeps Remove installed dependencies after a successful build" # fix flyspray feature request #2978 - echo " -R, --repackage Repackage contents of <startdir>/pkg without building" + echo " -R, --repackage Repackage contents of pkg/ without building" echo " -s, --syncdeps Install missing dependencies with pacman" echo " -S, --sudosync Install missing dependencies with pacman and sudo" echo Index: pacman-lib/src/pacman/pacman.c diff -u pacman-lib/src/pacman/pacman.c:1.88 pacman-lib/src/pacman/pacman.c:1.89 --- pacman-lib/src/pacman/pacman.c:1.88 Sun Feb 4 03:30:13 2007 +++ pacman-lib/src/pacman/pacman.c Thu Feb 8 00:24:18 2007 @@ -88,11 +88,11 @@ printf(_("usage: %s {-h --help}\n"), myname); printf(_(" %s {-V --version}\n"), myname); printf(_(" %s {-A --add} [options] <file>\n"), myname); - printf(_(" %s {-R --remove} [options] <package>\n"), myname); - printf(_(" %s {-U --upgrade} [options] <file>\n"), myname); printf(_(" %s {-F --freshen} [options] <file>\n"), myname); printf(_(" %s {-Q --query} [options] [package]\n"), myname); + printf(_(" %s {-R --remove} [options] <package>\n"), myname); printf(_(" %s {-S --sync} [options] [package]\n"), myname); + printf(_(" %s {-U --upgrade} [options] <file>\n"), myname); printf(_("\nuse '%s --help' with other options for more syntax\n"), myname); } else { if(op == PM_OP_ADD) {

1 0

[pacman-dev] CVS update of pacman-lib/src/pacman (package.c)
by dan＠archlinux.org 08 Feb '07

08 Feb '07

Date: Wednesday, February 7, 2007 @ 20:12:48 Author: dan Path: /home/cvs-pacman/pacman-lib/src/pacman Modified: package.c (1.27 -> 1.28) Fix newlines for real, and add a missing _() gettext wrapper. -----------+ package.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) Index: pacman-lib/src/pacman/package.c diff -u pacman-lib/src/pacman/package.c:1.27 pacman-lib/src/pacman/package.c:1.28 --- pacman-lib/src/pacman/package.c:1.27 Tue Feb 6 17:36:14 2007 +++ pacman-lib/src/pacman/package.c Wed Feb 7 20:12:48 2007 @@ -97,9 +97,10 @@ /* Print additional package info if info flag passed more than once */ if(level > 1) { /* call new backup function */ - dump_pkg_backups(pkg); printf("\n"); + dump_pkg_backups(pkg); } + printf("\n"); } /* Display the content of a sync package @@ -145,7 +146,7 @@ { alpm_list_t *i; const char *root = alpm_option_get_root(); - printf("\nBackup Files :\n"); + printf(_("Backup Files :\n")); for(i = alpm_pkg_get_backup(pkg); i; i = alpm_list_next(i)) { struct stat buf; char path[PATH_MAX];

1 0

[pacman-dev] CVS update of pacman-lib (TODO.aaron)
by Aaron Griffin 08 Feb '07

08 Feb '07

Date: Wednesday, February 7, 2007 @ 13:09:46 Author: aaron Path: /home/cvs-pacman/pacman-lib Modified: TODO.aaron (1.14 -> 1.15) ------------+ TODO.aaron | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) Index: pacman-lib/TODO.aaron diff -u pacman-lib/TODO.aaron:1.14 pacman-lib/TODO.aaron:1.15 --- pacman-lib/TODO.aaron:1.14 Wed Jan 31 03:10:01 2007 +++ pacman-lib/TODO.aaron Wed Feb 7 13:09:46 2007 @@ -1,5 +1,13 @@ == This is my custom TODO file == +* Dan and I both have personal TODOs. Perhaps we should kill off TODO and + TODO.autoconf + +* Look into other VCSs to use. The main CVS repo will remain, but having a + distributed system to allow for easy patching/pushing/pulling would be nice + - monotone and mercurial look like the top contenders in my book, but I need + to evaluate both a bit more. + * Make sure all the alpm_list_t changes are valid (especially alpm_list_free) * src/pacman: @@ -41,6 +49,28 @@ * pacman: fixup doxygen documentation for public interface +* libalpm: just because a function is in alpm.h doesn't mean it needs to be in + alpm.c - we should move functions around where they should be. In fact, + alpm.c might not be needed at all, if things were organized properly. + +* feature for 3.1: package file hooks * + I've been planning on this one for some time. Here's a simple rundown: + in /etc/pacman.d/hooks: + Hook /usr/include/* : /usr/bin/ctags -R /usr/include/*.h -f /usr/include/systags + This will allow us to make "global hooks" to simplify a lot of repetitive + install files (scrollkeeper, depmod, etc). This also allows us to move + ldconfig out of pacman entirely. + possible: /etc/pacman.hooks/* files for hooks, so packages can add them too + +* feature for 3.1: multiple search/match types + option: MatchType regex (current way) + MatchType fnmatch (use fnmatch to match things like 'pacman -S gnome*') + MatchType plain (no matching. expect plain text). + +* feature for 3.1: revamp the autotools system. I'd LOVE to use a manual system + like wmii and friends do. It'd be real nice if we could just do away with + autotools altogether. + **** BUGS **** * Removal of conflicts on -A and -U (INCOMPLETE) * gensync: get all info from packages instead of PKGBUILDs

6 12

[pacman-dev] Compilation warnings
by Dan McGee 08 Feb '07

08 Feb '07

These have been in the compile output for a while, perhaps we should look into it. I have a guess that it may be related to libdownload not installing a .la file (and it is also missing .so symlinks, compare to libarchive for example). If anyone else knows more about it, feel free to add your input. -Dan <snip> creating pacman /bin/sh ../../libtool --tag=CC --mode=link ccache cc -D_GNU_SOURCE -I../../lib/libalpm -g -O2 -D'PACCONF="/etc/pacman.conf"' -g -Wall -Werror -std=c99 -DPACMAN_DEBUG -g -O2 -D'PACCONF="/etc/pacman.conf"' -g -Wall -Werror -std=c99 -DPACMAN_DEBUG -lmcheck -o pacman.static -lmcheck -all-static util.o log.o package.o downloadprog.o trans.o add.o remove.o upgrade.o query.o sync.o conf.o deptest.o pacman.o -L../../lib/libalpm/.libs/ -ldownload -lalpm ccache cc -D_GNU_SOURCE -I../../lib/libalpm -g -O2 -DPACCONF=\"/etc/pacman.conf\" -g -Wall -Werror -std=c99 -DPACMAN_DEBUG -g -O2 -DPACCONF=\"/etc/pacman.conf\" -g -Wall -Werror -std=c99 -DPACMAN_DEBUG -o pacman.static -static util.o log.o package.o downloadprog.o trans.o add.o remove.o upgrade.o query.o sync.o conf.o deptest.o pacman.o -L/home/dmcgee/projects/pacman-lib/org.archlinux.pacman/lib/libalpm/.libs /home/dmcgee/projects/pacman-lib/org.archlinux.pacman/lib/libalpm/.libs/libalpm.a -lmcheck /usr/lib/libarchive.a -lz -lbz2 -lattr -lacl -ldownload -lm /usr/lib/libarchive.a(libarchive_la-archive_read_extract.o): In function `lookup_gid': (.text+0x69e): warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/libarchive.a(libarchive_la-archive_read_extract.o): In function `lookup_uid': (.text+0x5cf): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../libdownload.a(common.o): In function `_download_netrc_auth': (.text+0x47b): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../libdownload.a(common.o): In function `_download_bind': (.text+0x1d6): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../libdownload.a(common.o): In function `_download_default_port': (.text+0x277): warning: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

3 2

[pacman-dev] CVS update of pacman-lib (configure.ac)
by dan＠archlinux.org 08 Feb '07

08 Feb '07

Date: Wednesday, February 7, 2007 @ 18:03:30 Author: dan Path: /home/cvs-pacman/pacman-lib Modified: configure.ac (1.29 -> 1.30) Forgot to remove a few files from configure.ac --------------+ configure.ac | 4 ---- 1 file changed, 4 deletions(-) Index: pacman-lib/configure.ac diff -u pacman-lib/configure.ac:1.29 pacman-lib/configure.ac:1.30 --- pacman-lib/configure.ac:1.29 Wed Feb 7 17:29:21 2007 +++ pacman-lib/configure.ac Wed Feb 7 18:03:30 2007 @@ -225,10 +225,6 @@ src/util/Makefile scripts/Makefile doc/Makefile -doc/makepkg.8 -doc/libalpm.3 -doc/pacman.8 -doc/hu/Makefile etc/Makefile etc/makepkg.conf etc/pacman.conf

1 0

[pacman-dev] CVS update of pacman-lib (16 files)
by dan＠archlinux.org 07 Feb '07

07 Feb '07

Date: Wednesday, February 7, 2007 @ 17:29:22 Author: dan Path: /home/cvs-pacman/pacman-lib Modified: Makefile.am (1.9 -> 1.10) configure.ac (1.28 -> 1.29) doc/Makefile.am (1.11 -> 1.12) doc/libalpm.3 (1.2 -> 1.3) doc/makepkg.8 (1.2 -> 1.3) doc/pacman.8 (1.2 -> 1.3) Removed: doc/addendum.8.hu (1.1) doc/hu/.cvsignore (1.1) doc/hu/Makefile.am (1.3) doc/libalpm.3.in (1.2) doc/makepkg.8.in (1.5) doc/pacman.8.in (1.10) doc/po/.cvsignore (1.1) doc/po/hu.po (1.6) doc/po/pacman.pot (1.6) doc/po4a.cfg (1.3) Greatly simplify the way our non-existant translated manpages were being made. Ripped out all the po4a stuff, letting us cut down on yet another makedepends. Also moved all of the manpages to non-.in names. --------------------+ Makefile.am | 2 configure.ac | 42 doc/Makefile.am | 16 doc/addendum.8.hu | 3 doc/hu/.cvsignore | 4 doc/hu/Makefile.am | 7 doc/libalpm.3 | 21 doc/libalpm.3.in | 21 doc/makepkg.8 | 455 ++++++++ doc/makepkg.8.in | 455 -------- doc/pacman.8 | 334 ++++++ doc/pacman.8.in | 334 ------ doc/po/.cvsignore | 6 doc/po/hu.po | 2595 --------------------------------------------------- doc/po/pacman.pot | 2563 -------------------------------------------------- doc/po4a.cfg | 11 16 files changed, 815 insertions(+), 6054 deletions(-) Index: pacman-lib/Makefile.am diff -u pacman-lib/Makefile.am:1.9 pacman-lib/Makefile.am:1.10 --- pacman-lib/Makefile.am:1.9 Thu Feb 1 14:47:39 2007 +++ pacman-lib/Makefile.am Wed Feb 7 17:29:21 2007 @@ -1,4 +1,4 @@ -SUBDIRS = lib/libalpm src/util src/pacman scripts doc doc/hu etc +SUBDIRS = lib/libalpm src/util src/pacman scripts doc etc EXTRA_DIST = \ ChangeLog \ Index: pacman-lib/configure.ac diff -u pacman-lib/configure.ac:1.28 pacman-lib/configure.ac:1.29 --- pacman-lib/configure.ac:1.28 Thu Feb 1 14:50:07 2007 +++ pacman-lib/configure.ac Wed Feb 7 17:29:21 2007 @@ -54,31 +54,11 @@ AC_HELP_STRING([--enable-man2html], [Build html docs via man2html]), [wantman2html=$enableval], [wantman2html=no]) -dnl Help line for po4a -AC_ARG_ENABLE(po4a, - AC_HELP_STRING([--disable-po4a], [Build localized manpages via po4a]), - [wantpo4a=$enableval], [wantpo4a=yes]) - dnl Help line for doxygen AC_ARG_ENABLE(doxygen, AC_HELP_STRING([--disable-doxygen], [Build API docs via Doxygen]), [wantdoxygen=$enableval], [wantdoxygen=yes]) -dnl Help line for python -AC_ARG_ENABLE(python, - AC_HELP_STRING([--disable-python], [Build Python bindings]), - [wantpython=$enableval], [wantpython=yes]) - -dnl Help line for perl -AC_ARG_ENABLE(perl, - AC_HELP_STRING([--disable-perl], [Build Perl bindings]), - [wantperl=$enableval], [wantperl=yes]) - -dnl Help line for java -AC_ARG_ENABLE(java, - AC_HELP_STRING([--disable-java], [Build Java bindings]), - [wantjava=$enableval], [wantjava=yes]) - dnl Check for architecture case "$host" in i686-*) AC_DEFINE_UNQUOTED([CARCH], ["i686"], [Architecture]) @@ -173,27 +153,6 @@ AC_MSG_RESULT(not requested by configure) fi -dnl Check for po4a binary -AC_MSG_CHECKING(for support po4a) -if test x$wantpo4a = xyes ; then - AC_CHECK_PROGS([PO4A], [po4a]) - AM_CONDITIONAL(HAS_PO4A, test $PO4A) - if test $PO4A ; then - AC_DEFINE([HAS_PO4A], [TRUE], [Enabled PO4A (localization support for manpages)]) - AC_MSG_RESULT(yes) - POSTATUS="yes, path: `which $PO4A`" - else - AC_DEFINE([HAS_PO4A], [FALSE], [Disabled PO4A (localization support for manpages)]) - AC_MSG_RESULT(no, po4a binary missing) - POSTATUS="no, missing po4a binary" - fi -else - AM_CONDITIONAL(HAS_PO4A, test $PO4A) - AC_DEFINE([HAS_PO4A], [FALSE], [Not specified at configure line]) - AC_MSG_RESULT(not requested by configure) - POSTATUS="no, disabled by configure" -fi - dnl Check for doxygen support if test x$wantdoxygen = xyes ; then AC_CHECK_PROGS([DOXYGEN], [doxygen]) @@ -295,7 +254,6 @@ Architecture CHOST : ${CHOST} Doxygen support : ${DOXYSTATUS} - Manpage localization : ${POSTATUS} debug support : ${debug} " Index: pacman-lib/doc/Makefile.am diff -u pacman-lib/doc/Makefile.am:1.11 pacman-lib/doc/Makefile.am:1.12 --- pacman-lib/doc/Makefile.am:1.11 Tue Feb 6 15:23:41 2007 +++ pacman-lib/doc/Makefile.am Wed Feb 7 17:29:21 2007 @@ -1,14 +1,5 @@ -all: po4a makepkg.8 PKGBUILD.5 pacman.8 +all: makepkg.8 PKGBUILD.5 pacman.8 -SUBDIRS = hu - -po4a: -if HAS_PO4A - @$(NORMAL_INSTALL) - po4a -k 0 --variable srcdir=$(srcdir) $(srcdir)/po4a.cfg -endif - -# DIST_SUBDIRS if HAS_MAN2HTML makepkg.8: man2html makepkg.8 > html/makepkg.8.html @@ -22,8 +13,9 @@ clean: rm -f html/*.html - rm -f hu/*.8 rm -f man3/*.3 + rm -f man5/*.5 + rm -f man8/*.8 man_MANS = pacman.8 makepkg.8 PKGBUILD.5 libalpm.3 @@ -31,4 +23,4 @@ man_MANS += *.3 endif -EXTRA_DIST = $(man_MANS) po4a.cfg +EXTRA_DIST = $(man_MANS) Index: pacman-lib/doc/addendum.8.hu diff -u pacman-lib/doc/addendum.8.hu:1.1 pacman-lib/doc/addendum.8.hu:removed --- pacman-lib/doc/addendum.8.hu:1.1 Sun Oct 15 14:58:24 2006 +++ pacman-lib/doc/addendum.8.hu Wed Feb 7 17:29:23 2007 @@ -1,3 +0,0 @@ -PO4A-HEADER:mode=after;position=SZERZÕ;beginboundary=.SH -.SH FORDÍTÁS -Dvornik László <dvornik(a)gnome.hu>. Index: pacman-lib/doc/hu/.cvsignore diff -u pacman-lib/doc/hu/.cvsignore:1.1 pacman-lib/doc/hu/.cvsignore:removed --- pacman-lib/doc/hu/.cvsignore:1.1 Tue Jan 16 22:40:08 2007 +++ pacman-lib/doc/hu/.cvsignore Wed Feb 7 17:29:23 2007 @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.3 -*.8 Index: pacman-lib/doc/hu/Makefile.am diff -u pacman-lib/doc/hu/Makefile.am:1.3 pacman-lib/doc/hu/Makefile.am:removed --- pacman-lib/doc/hu/Makefile.am:1.3 Tue Feb 6 15:23:41 2007 +++ pacman-lib/doc/hu/Makefile.am Wed Feb 7 17:29:23 2007 @@ -1,7 +0,0 @@ -AUTOMAKE_OPTIONS=foreign - -mandir = @mandir@/hu -man_MANS = pacman.8 makepkg.8 PKGBUILD.5 -$(man_MANS): - -EXTRA_DIST = pacman.8 makepkg.8 PKGBUILD.5 Index: pacman-lib/doc/libalpm.3 diff -u /dev/null pacman-lib/doc/libalpm.3:1.3 --- /dev/null Wed Feb 7 17:29:23 2007 +++ pacman-lib/doc/libalpm.3 Wed Feb 7 17:29:21 2007 @@ -0,0 +1,21 @@ +.TH libalpm 3 "07 Jan 2007" "libalpm @PM_VERSION@" "" +.SH NAME + libalpm \- Arch Linux Package Management library +.SH SYNOPSIS +For ease of access, the libalpm manual has been split up into several sections. + +.nf +alpm_databases Database Functions +alpm_interface Interface Functions +alpm_list List Functions +alpm_log Logging Functions +alpm_misc Miscellaneous Functions +alpm_packages Package Functions +alpm_sync Sync Functions +alpm_trans Transaction Functions +.fi + +.SH AUTHOR +.nf +Judd Vinet <jvinet(a)zeroflux.org> +.fi Index: pacman-lib/doc/libalpm.3.in diff -u pacman-lib/doc/libalpm.3.in:1.2 pacman-lib/doc/libalpm.3.in:removed --- pacman-lib/doc/libalpm.3.in:1.2 Thu Jan 11 12:32:49 2007 +++ pacman-lib/doc/libalpm.3.in Wed Feb 7 17:29:23 2007 @@ -1,21 +0,0 @@ -.TH libalpm 3 "07 Jan 2007" "libalpm @PM_VERSION@" "" -.SH NAME - libalpm \- Arch Linux Package Management library -.SH SYNOPSIS -For ease of access, the libalpm manual has been split up into several sections. - -.nf -alpm_databases Database Functions -alpm_interface Interface Functions -alpm_list List Functions -alpm_log Logging Functions -alpm_misc Miscellaneous Functions -alpm_packages Package Functions -alpm_sync Sync Functions -alpm_trans Transaction Functions -.fi - -.SH AUTHOR -.nf -Judd Vinet <jvinet(a)zeroflux.org> -.fi Index: pacman-lib/doc/makepkg.8 diff -u /dev/null pacman-lib/doc/makepkg.8:1.3 --- /dev/null Wed Feb 7 17:29:23 2007 +++ pacman-lib/doc/makepkg.8 Wed Feb 7 17:29:21 2007 @@ -0,0 +1,455 @@ +.TH makepkg 8 "January 30, 2006" "makepkg #VERSION#" "" +.SH NAME +makepkg \- package build utility +.SH SYNOPSIS +\fBmakepkg [options]\fP +.SH DESCRIPTION +\fBmakepkg\fP will build packages for you. All it needs is +a build-capable linux platform, wget, and some build scripts. The advantage +to a script-based build is that you only really do the work once. Once you +have the build script for a package, you just need to run makepkg and it +will do the rest: download and validate source files, check dependencies, +configure the buildtime 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. +.SH BUILD PROCESS (or How To Build Your Own Packages) +Start in an isolated directory (ie, it's not used for anything other +than building this package). The build script should be called PKGBUILD +and it should bear resemblance to the example below. + +\fBNOTE:\fP If you have a local copy of the Arch Build System (ABS) tree +on your computer, you can copy the PKGBUILD.proto file to your new package +build directory and edit it from there. To acquire/sync the ABS tree, use +the \fBabs\fP script included with pacman/makepkg. + +.TP +.TP +.SH PKGBUILD Example: +.RS +.nf +pkgname=modutils +pkgver=2.4.25 +pkgrel=1 +pkgdesc="Utilities for inserting and removing modules from the linux kernel" +url="http://www.kernel.org" +backup=(etc/modules.conf) +makedepends=('bash' 'mawk') +depends=('glibc' 'zlib') +source=(ftp://ftp.kernel.org/pub/linux/utils/kernel/$pkgname/v2.4/$pkgname-$pkgver.tar.bz2 \\ + modules.conf) +md5sums=('2c0cca3ef6330a187c6ef4fe41ecaa4d' \\ + '35175bee593a7cc7d6205584a94d8625') + +build() { + cd $startdir/src/$pkgname-$pkgver + ./configure --prefix=/usr --enable-insmod-static + make || return 1 + make prefix=$startdir/pkg/usr install + mv $startdir/pkg/usr/sbin $startdir/pkg + mkdir -p $startdir/pkg/etc + cp ../modules.conf $startdir/pkg/etc +} +.fi +.RE + +As you can see, the setup is fairly simple. The first three lines define +the package name and version info. They also define the final package name +which will be of the form \fI$pkgname-$pkgver-$pkgrel.pkg.tar.gz\fP. The fourth +line provides a brief description of the package. These four lines should +be present in every PKGBUILD script. + +The line with \fIbackup=\fP specifies files that should be treated specially +when removing or upgrading packages. See \fBHANDLING CONFIG FILES\fP in +the \fIpacman\fP manpage for more information on this. + +Lines 7 and 8 list the dependencies for this package. The \fIdepends\fP array +specifies the run-time dependencies and \fImakedepends\fP specifies the build-time +dependencies. In order to run the package, \fIdepends\fP must be satisfied. To +build the package, \fBall\fP dependencies must be satisifed first. makepkg +will check this before attempting to build the package. + +The \fIsource\fP array tells makepkg which files to download/extract before compiling +begins. The \fImd5sums\fP array provides md5sums for each of these files. These +are used to validate the integrity of the source files. + +Once your PKGBUILD is created, you can run \fImakepkg\fP from the build directory. +makepkg will then check dependencies and look for the source files required to +build. If some are missing it will attempt to download them, provided there is +a fully-qualified URL in the \fIsource\fP array. + +The sources are then extracted into a directory called ./src and +the \fIbuild\fP function is called. This is where all package configuration, +building, and installing should be done. Any customization will likely take +place here. + +After a package is built, the \fIbuild\fP function must install the package +files into a special package root, which can be referenced by \fB$startdir/pkg\fP +in the \fIbuild\fP function. The typical way to do this is one of the following: +.RS +.nf + +make DESTDIR=$startdir/pkg install + +or + +make prefix=$startdir/pkg/usr install + +.fi +.RE +Notice that the "/usr" portion should be present with "prefix", but not "DESTDIR". +"DESTDIR" is the favorable option to use, but not all Makefiles support it. Use +"prefix" only when "DESTDIR" is unavailable. + +Once the package is successfully installed into the package root, \fImakepkg\fP +will remove some directories (as per Arch Linux package guidelines; if you use +this elsewhere, feel free to change it) like /usr/doc and /usr/info. It will +then strip debugging info from libraries and binaries and generate a meta-info +file. Finally, it will compress everything into a .pkg.tar.gz file and leave it +in the directory you ran \fBmakepkg\fP from. + +At this point you should have a package file in the current directory, named +something like name-version-release.pkg.tar.gz. Done! + +.SH Install/Upgrade/Remove Scripting +Pacman has the ability to store and execute a package-specific script when it +installs, removes, or upgrades a package. This allows a package to "configure +itself" after installation and do the opposite right before it is removed. + +The exact time the script is run varies with each operation: +.TP +.B pre_install +script is run right before files are extracted. + +.TP +.B post_install +script is run right after files are extracted. + +.TP +.B pre_upgrade +script is run right before files are extracted. + +.TP +.B post_upgrade +script is run after files are extracted. + +.TP +.B pre_remove +script is run right before files are removed. + +.TP +.B post_remove +script is run right after files are removed. + +.RE +To use this feature, just create a file (eg, pkgname.install) and put it in +the same directory as the PKGBUILD script. Then use the \fIinstall\fP directive: +.RS +.nf +install=pkgname.install +.fi +.RE + +The install script does not need to be specified in the \fIsource\fP array. + +.TP +.TP +.SH Install scripts must follow this format: +.RS +.nf +# arg 1: the new package version +pre_install() { + # + # do pre-install stuff here + # + /bin/true +} + +# arg 1: the new package version +post_install() { + # + # do post-install stuff here + # + /bin/true +} + +# arg 1: the new package version +# arg 2: the old package version +pre_upgrade() { + # + # do pre-upgrade stuff here + # + /bin/true +} + +# arg 1: the new package version +# arg 2: the old package version +post_upgrade() { + # + # do post-upgrade stuff here + # + /bin/true +} + +# arg 1: the old package version +pre_remove() { + # + # do pre-remove stuff here + # + /bin/true +} + +# arg 1: the old package version +post_remove() { + # + # do post-remove stuff here + # + /bin/true +} + +op=$1 +shift +$op $* +.fi +.RE + +This template is also available in your ABS tree (/var/abs/install.proto). + +.SH PKGBUILD Directives +.TP +.B pkgname +The name of the package. This has be a unix-friendly name as it will be +used in the package filename. + +.TP +.B pkgver +This is the version of the software as released from the author (eg, 2.7.1). + +.TP +.B pkgrel +This is the release number specific to Arch Linux packages. + +.TP +.B pkgdesc +This should be a brief description of the package and its functionality. + +.TP +.B options +This array allows you to override some of makepkg's default behaviour +when building packages. To set an option, just include the option name +in the \fBoptions\fP array. +.TP +.RS +\fIAvailable Options:\fP +.RS +.TP +.B FORCE +force the package to be upgraded by \fB--sysupgrade\fP, even +if its an older version. +.TP +.B KEEPDOCS +do not remove /usr/share/doc and /usr/share/info directories. +.TP +.B NOSTRIP +do not strip debugging symbols from binaries and libraries. +.RE +.RE + +.TP +.B url +This field contains an optional URL that is associated with the piece of software +being packaged. This is typically the project's website. + +.TP +.B license +This field specifies the license(s) that apply to the package. Commonly-used +licenses are typically found in \fI/usr/share/licenses/common\fP. If you +see the package's license there, simply reference it in the license field +(eg, \fBlicense="GPL"\fP). If the package provides a license not found in +\fI/usr/share/licenses/common\fP, then you should include the license in +the package itself and set \fBlicense="custom"\fP or \fBlicense="custom:LicenseName"\fP. +The license itself should be placed in a directory called +\fI$startdir/pkg/usr/share/licenses/$pkgname\fP. +.TP +.RE +If multiple licenses are applied, use the array form: \fBlicense=('GPL' 'FDL')\fP + +.TP +.B install +Specifies a special install script that is to be included in the package. +This file should reside in the same directory as the PKGBUILD, and will be +copied into the package by makepkg. It does not need to be included in the +\fIsource\fP array. (eg, install=modutils.install) + +.TP +.B source \fI(array)\fP +The \fIsource\fP line is an array of source files required to build the +package. Source files must reside in the same directory as the PKGBUILD +file, unless they have a fully-qualified URL. Then if the source file +does not already exist in /var/cache/pacman/src, the file is downloaded +by wget. + +.TP +.B md5sums \fI(array)\fP +If this field is present, it should contain an MD5 hash for every source file +specified in the \fIsource\fP array (in the same order). makepkg will use +this to verify source file integrity during subsequent builds. To easily +generate md5sums, first build using the PKGBUILD then run +\fBmakepkg -g >>PKGBUILD\fP. Then you can edit the PKGBUILD and move the +\fImd5sums\fP line from the bottom to an appropriate location. + +.TP +.B groups \fI(array)\fP +This is an array of symbolic names that represent groups of packages, allowing +you to install multiple packages by requesting a single target. For example, +one could install all KDE packages by installing the 'kde' group. + +.TP +.B backup \fI(array)\fP +A space-delimited array of filenames (without a preceding slash). The +\fIbackup\fP line will be propagated to the package meta-info file for +pacman. This will designate all files listed there to be backed up if this +package is ever removed from a system. See \fBHANDLING CONFIG FILES\fP in +the \fIpacman\fP manpage for more information. + +.TP +.B depends \fI(array)\fP +An array of packages that this package depends on to build and run. Packages +in this list should be surrounded with single quotes and contain at least the +package name. They can also include a version requirement of the form +\fBname<>version\fP, where <> is one of these three comparisons: \fB>=\fP +(greater than equal to), \fB<=\fP (less than or equal to), or \fB=\fP (equal to). +See the PKGBUILD example above for an example of the \fIdepends\fP directive. + +.TP +.B makedepends \fI(array)\fP +An array of packages that this package depends on to build (ie, not required +to run). Packages in this list should follow the same format as \fIdepends\fP. + +.TP +.B conflicts \fI(array)\fP +An array of packages that will conflict with this package (ie, they cannot both +be installed at the same time). This directive follows the same format as +\fIdepends\fP except you cannot specify versions here, only package names. + +.TP +.B provides \fI(array)\fP +An array of "virtual provisions" that this package provides. This allows a package +to provide dependency names other than it's own package name. For example, the +kernel-scsi and kernel-ide packages can each provide 'kernel' which allows packages +to simply depend on 'kernel' rather than "kernel-scsi OR kernel-ide OR ..." + +.TP +.B replaces \fI(array)\fP +This is an array of packages that this package should replace, and can be used to handle +renamed/combined packages. For example, if the kernel package gets renamed +to kernel-ide, then subsequent 'pacman -Syu' calls will not pick up the upgrade, due +to the differing package names. \fIreplaces\fP handles this. + +.SH MAKEPKG OPTIONS +.TP +.B "\-b, \-\-builddeps" +Build missing dependencies from source. When makepkg finds missing build-time or +run-time dependencies, it will look for the dependencies' PKGBUILD files under +$ABSROOT (set in your /etc/makepkg.conf). If it finds them it will +run another copy of makepkg to build and install the missing dependencies. +The child makepkg calls will be made with the \fB-b\fP and \fB-i\fP options. +.TP +.B "\-B, \-\-noccache" +Do not use ccache during build. +.TP +.B "\-c, \-\-clean" +Clean up leftover work files/directories after a successful build. +.TP +.B "\-C, \-\-cleancache" +Removes all source files from the cache directory to free up diskspace. +.TP +.B "\-d, \-\-nodeps" +Do not perform any dependency checks. This will let you override/ignore any +dependencies required. There's a good chance this option will break the build +process if all of the dependencies aren't installed. +.TP +.B "\-e, \-\-noextract" +Do not extract source files. Instead, use whatever already exists in the +src/ directory. This is handy if you want to go into src and manually +patch/tweak code, then make a package out of the result. +.TP +.B "\-f, \-\-force" +\fBmakepkg\fP will not build a package if a \fIpkgname-pkgver-pkgrel.pkg.tar.gz\fP +file already exists in the build directory. You can override this behaviour with +the \fB--force\fP switch. +.TP +.B "\-g, \-\-genmd5" +Download all source files (if required) and use \fImd5sum\fP to generate md5 hashes +for each of them. You can then redirect the output into your PKGBUILD for source +validation (makepkg -g >>PKGBUILD). +.TP +.B "\-h, \-\-help" +Output syntax and commandline options. +.TP +.B "\-i, \-\-install" +Install/Upgrade the package after a successful build. +.TP +.B "\-j <jobs>" +Sets MAKEFLAGS="-j<jobs>" before building the package. This is useful for overriding +the MAKEFLAGS setting in /etc/makepkg.conf. +.TP +.B "\-m, \-\-nocolor" +Disable color in output messages +.TP +.B "\-n, \-\-nostrip" +Do not strip binaries and libraries. +.TP +.B "\-o, \-\-nobuild" +Download and extract files only, do not build. +.TP +.B "\-p <buildscript>" +Read the package script \fI<buildscript>\fP instead of the default (\fIPKGBUILD\fP). +.TP +.B "\-r, \-\-rmdeps" +Upon successful build, remove any dependencies installed by makepkg/pacman during +dependency auto-resolution (using \fB-b\fP or \fB-s\fP). +.TP +.B "\-s, \-\-syncdeps" +Install missing dependencies using pacman. When makepkg finds missing build-time +or run-time dependencies, it will run pacman to try and resolve them. If successful, +pacman will download the missing packages from a package repository and +install them for you. +.TP +.B "\-S, \-\-sudosync" +Install missing dependencies using pacman and sudo. This is the same as \fB-s\fP +except that makepkg will call pacman with sudo. This means you don't have to +build as root to use dependency auto-resolution. +.TP +.B "\-w <destdir>" +Write the resulting package file to the directory \fI<destdir>\fP instead of the +current working directory. +.TP +.B "\-\-noconfirm" +When calling pacman to resolve dependencies or conflicts, makepkg can pass +the \fI--noconfirm\fP option to it so it does not wait for any user +input before proceeding with operations. +.TP +.B "\-\-noprogressbar" +When calling pacman, makepkg can pass the \fI--noprogressbar\fP option to it. +This is useful if one is directing makepkg's output to a non-terminal (ie, a file). + +.SH CONFIGURATION +Configuration options are stored in \fI/etc/makepkg.conf\fP. This file is parsed +as a bash script, so you can export any special compiler flags you wish +to use. This is helpful for building for different architectures, or with +different optimizations. + +\fBNOTE:\fP This does not guarantee that all package Makefiles will use +your exported variables. Some of them are flaky... +.SH SEE ALSO +\fBpacman\fP is the package manager that uses packages built by makepkg. + +See the Arch Linux Documentation for package-building guidelines if you wish +to contribute packages to the Arch Linux project. +.SH AUTHOR +.nf +Judd Vinet <jvinet(a)zeroflux.org> +.fi Index: pacman-lib/doc/makepkg.8.in diff -u pacman-lib/doc/makepkg.8.in:1.5 pacman-lib/doc/makepkg.8.in:removed --- pacman-lib/doc/makepkg.8.in:1.5 Sun Oct 1 19:22:53 2006 +++ pacman-lib/doc/makepkg.8.in Wed Feb 7 17:29:23 2007 @@ -1,455 +0,0 @@ -.TH makepkg 8 "January 30, 2006" "makepkg #VERSION#" "" -.SH NAME -makepkg \- package build utility -.SH SYNOPSIS -\fBmakepkg [options]\fP -.SH DESCRIPTION -\fBmakepkg\fP will build packages for you. All it needs is -a build-capable linux platform, wget, and some build scripts. The advantage -to a script-based build is that you only really do the work once. Once you -have the build script for a package, you just need to run makepkg and it -will do the rest: download and validate source files, check dependencies, -configure the buildtime 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. -.SH BUILD PROCESS (or How To Build Your Own Packages) -Start in an isolated directory (ie, it's not used for anything other -than building this package). The build script should be called PKGBUILD -and it should bear resemblance to the example below. - -\fBNOTE:\fP If you have a local copy of the Arch Build System (ABS) tree -on your computer, you can copy the PKGBUILD.proto file to your new package -build directory and edit it from there. To acquire/sync the ABS tree, use -the \fBabs\fP script included with pacman/makepkg. - -.TP -.TP -.SH PKGBUILD Example: -.RS -.nf -pkgname=modutils -pkgver=2.4.25 -pkgrel=1 -pkgdesc="Utilities for inserting and removing modules from the linux kernel" -url="http://www.kernel.org" -backup=(etc/modules.conf) -makedepends=('bash' 'mawk') -depends=('glibc' 'zlib') -source=(ftp://ftp.kernel.org/pub/linux/utils/kernel/$pkgname/v2.4/$pkgname-$pkgver.tar.bz2 \\ - modules.conf) -md5sums=('2c0cca3ef6330a187c6ef4fe41ecaa4d' \\ - '35175bee593a7cc7d6205584a94d8625') - -build() { - cd $startdir/src/$pkgname-$pkgver - ./configure --prefix=/usr --enable-insmod-static - make || return 1 - make prefix=$startdir/pkg/usr install - mv $startdir/pkg/usr/sbin $startdir/pkg - mkdir -p $startdir/pkg/etc - cp ../modules.conf $startdir/pkg/etc -} -.fi -.RE - -As you can see, the setup is fairly simple. The first three lines define -the package name and version info. They also define the final package name -which will be of the form \fI$pkgname-$pkgver-$pkgrel.pkg.tar.gz\fP. The fourth -line provides a brief description of the package. These four lines should -be present in every PKGBUILD script. - -The line with \fIbackup=\fP specifies files that should be treated specially -when removing or upgrading packages. See \fBHANDLING CONFIG FILES\fP in -the \fIpacman\fP manpage for more information on this. - -Lines 7 and 8 list the dependencies for this package. The \fIdepends\fP array -specifies the run-time dependencies and \fImakedepends\fP specifies the build-time -dependencies. In order to run the package, \fIdepends\fP must be satisfied. To -build the package, \fBall\fP dependencies must be satisifed first. makepkg -will check this before attempting to build the package. - -The \fIsource\fP array tells makepkg which files to download/extract before compiling -begins. The \fImd5sums\fP array provides md5sums for each of these files. These -are used to validate the integrity of the source files. - -Once your PKGBUILD is created, you can run \fImakepkg\fP from the build directory. -makepkg will then check dependencies and look for the source files required to -build. If some are missing it will attempt to download them, provided there is -a fully-qualified URL in the \fIsource\fP array. - -The sources are then extracted into a directory called ./src and -the \fIbuild\fP function is called. This is where all package configuration, -building, and installing should be done. Any customization will likely take -place here. - -After a package is built, the \fIbuild\fP function must install the package -files into a special package root, which can be referenced by \fB$startdir/pkg\fP -in the \fIbuild\fP function. The typical way to do this is one of the following: -.RS -.nf - -make DESTDIR=$startdir/pkg install - -or - -make prefix=$startdir/pkg/usr install - -.fi -.RE -Notice that the "/usr" portion should be present with "prefix", but not "DESTDIR". -"DESTDIR" is the favorable option to use, but not all Makefiles support it. Use -"prefix" only when "DESTDIR" is unavailable. - -Once the package is successfully installed into the package root, \fImakepkg\fP -will remove some directories (as per Arch Linux package guidelines; if you use -this elsewhere, feel free to change it) like /usr/doc and /usr/info. It will -then strip debugging info from libraries and binaries and generate a meta-info -file. Finally, it will compress everything into a .pkg.tar.gz file and leave it -in the directory you ran \fBmakepkg\fP from. - -At this point you should have a package file in the current directory, named -something like name-version-release.pkg.tar.gz. Done! - -.SH Install/Upgrade/Remove Scripting -Pacman has the ability to store and execute a package-specific script when it -installs, removes, or upgrades a package. This allows a package to "configure -itself" after installation and do the opposite right before it is removed. - -The exact time the script is run varies with each operation: -.TP -.B pre_install -script is run right before files are extracted. - -.TP -.B post_install -script is run right after files are extracted. - -.TP -.B pre_upgrade -script is run right before files are extracted. - -.TP -.B post_upgrade -script is run after files are extracted. - -.TP -.B pre_remove -script is run right before files are removed. - -.TP -.B post_remove -script is run right after files are removed. - -.RE -To use this feature, just create a file (eg, pkgname.install) and put it in -the same directory as the PKGBUILD script. Then use the \fIinstall\fP directive: -.RS -.nf -install=pkgname.install -.fi -.RE - -The install script does not need to be specified in the \fIsource\fP array. - -.TP -.TP -.SH Install scripts must follow this format: -.RS -.nf -# arg 1: the new package version -pre_install() { - # - # do pre-install stuff here - # - /bin/true -} - -# arg 1: the new package version -post_install() { - # - # do post-install stuff here - # - /bin/true -} - -# arg 1: the new package version -# arg 2: the old package version -pre_upgrade() { - # - # do pre-upgrade stuff here - # - /bin/true -} - -# arg 1: the new package version -# arg 2: the old package version -post_upgrade() { - # - # do post-upgrade stuff here - # - /bin/true -} - -# arg 1: the old package version -pre_remove() { - # - # do pre-remove stuff here - # - /bin/true -} - -# arg 1: the old package version -post_remove() { - # - # do post-remove stuff here - # - /bin/true -} - -op=$1 -shift -$op $* -.fi -.RE - -This template is also available in your ABS tree (/var/abs/install.proto). - -.SH PKGBUILD Directives -.TP -.B pkgname -The name of the package. This has be a unix-friendly name as it will be -used in the package filename. - -.TP -.B pkgver -This is the version of the software as released from the author (eg, 2.7.1). - -.TP -.B pkgrel -This is the release number specific to Arch Linux packages. - -.TP -.B pkgdesc -This should be a brief description of the package and its functionality. - -.TP -.B options -This array allows you to override some of makepkg's default behaviour -when building packages. To set an option, just include the option name -in the \fBoptions\fP array. -.TP -.RS -\fIAvailable Options:\fP -.RS -.TP -.B FORCE -force the package to be upgraded by \fB--sysupgrade\fP, even -if its an older version. -.TP -.B KEEPDOCS -do not remove /usr/share/doc and /usr/share/info directories. -.TP -.B NOSTRIP -do not strip debugging symbols from binaries and libraries. -.RE -.RE - -.TP -.B url -This field contains an optional URL that is associated with the piece of software -being packaged. This is typically the project's website. - -.TP -.B license -This field specifies the license(s) that apply to the package. Commonly-used -licenses are typically found in \fI/usr/share/licenses/common\fP. If you -see the package's license there, simply reference it in the license field -(eg, \fBlicense="GPL"\fP). If the package provides a license not found in -\fI/usr/share/licenses/common\fP, then you should include the license in -the package itself and set \fBlicense="custom"\fP or \fBlicense="custom:LicenseName"\fP. -The license itself should be placed in a directory called -\fI$startdir/pkg/usr/share/licenses/$pkgname\fP. -.TP -.RE -If multiple licenses are applied, use the array form: \fBlicense=('GPL' 'FDL')\fP - -.TP -.B install -Specifies a special install script that is to be included in the package. -This file should reside in the same directory as the PKGBUILD, and will be -copied into the package by makepkg. It does not need to be included in the -\fIsource\fP array. (eg, install=modutils.install) - -.TP -.B source \fI(array)\fP -The \fIsource\fP line is an array of source files required to build the -package. Source files must reside in the same directory as the PKGBUILD -file, unless they have a fully-qualified URL. Then if the source file -does not already exist in /var/cache/pacman/src, the file is downloaded -by wget. - -.TP -.B md5sums \fI(array)\fP -If this field is present, it should contain an MD5 hash for every source file -specified in the \fIsource\fP array (in the same order). makepkg will use -this to verify source file integrity during subsequent builds. To easily -generate md5sums, first build using the PKGBUILD then run -\fBmakepkg -g >>PKGBUILD\fP. Then you can edit the PKGBUILD and move the -\fImd5sums\fP line from the bottom to an appropriate location. - -.TP -.B groups \fI(array)\fP -This is an array of symbolic names that represent groups of packages, allowing -you to install multiple packages by requesting a single target. For example, -one could install all KDE packages by installing the 'kde' group. - -.TP -.B backup \fI(array)\fP -A space-delimited array of filenames (without a preceding slash). The -\fIbackup\fP line will be propagated to the package meta-info file for -pacman. This will designate all files listed there to be backed up if this -package is ever removed from a system. See \fBHANDLING CONFIG FILES\fP in -the \fIpacman\fP manpage for more information. - -.TP -.B depends \fI(array)\fP -An array of packages that this package depends on to build and run. Packages -in this list should be surrounded with single quotes and contain at least the -package name. They can also include a version requirement of the form -\fBname<>version\fP, where <> is one of these three comparisons: \fB>=\fP -(greater than equal to), \fB<=\fP (less than or equal to), or \fB=\fP (equal to). -See the PKGBUILD example above for an example of the \fIdepends\fP directive. - -.TP -.B makedepends \fI(array)\fP -An array of packages that this package depends on to build (ie, not required -to run). Packages in this list should follow the same format as \fIdepends\fP. - -.TP -.B conflicts \fI(array)\fP -An array of packages that will conflict with this package (ie, they cannot both -be installed at the same time). This directive follows the same format as -\fIdepends\fP except you cannot specify versions here, only package names. - -.TP -.B provides \fI(array)\fP -An array of "virtual provisions" that this package provides. This allows a package -to provide dependency names other than it's own package name. For example, the -kernel-scsi and kernel-ide packages can each provide 'kernel' which allows packages -to simply depend on 'kernel' rather than "kernel-scsi OR kernel-ide OR ..." - -.TP -.B replaces \fI(array)\fP -This is an array of packages that this package should replace, and can be used to handle -renamed/combined packages. For example, if the kernel package gets renamed -to kernel-ide, then subsequent 'pacman -Syu' calls will not pick up the upgrade, due -to the differing package names. \fIreplaces\fP handles this. - -.SH MAKEPKG OPTIONS -.TP -.B "\-b, \-\-builddeps" -Build missing dependencies from source. When makepkg finds missing build-time or -run-time dependencies, it will look for the dependencies' PKGBUILD files under -$ABSROOT (set in your /etc/makepkg.conf). If it finds them it will -run another copy of makepkg to build and install the missing dependencies. -The child makepkg calls will be made with the \fB-b\fP and \fB-i\fP options. -.TP -.B "\-B, \-\-noccache" -Do not use ccache during build. -.TP -.B "\-c, \-\-clean" -Clean up leftover work files/directories after a successful build. -.TP -.B "\-C, \-\-cleancache" -Removes all source files from the cache directory to free up diskspace. -.TP -.B "\-d, \-\-nodeps" -Do not perform any dependency checks. This will let you override/ignore any -dependencies required. There's a good chance this option will break the build -process if all of the dependencies aren't installed. -.TP -.B "\-e, \-\-noextract" -Do not extract source files. Instead, use whatever already exists in the -src/ directory. This is handy if you want to go into src and manually -patch/tweak code, then make a package out of the result. -.TP -.B "\-f, \-\-force" -\fBmakepkg\fP will not build a package if a \fIpkgname-pkgver-pkgrel.pkg.tar.gz\fP -file already exists in the build directory. You can override this behaviour with -the \fB--force\fP switch. -.TP -.B "\-g, \-\-genmd5" -Download all source files (if required) and use \fImd5sum\fP to generate md5 hashes -for each of them. You can then redirect the output into your PKGBUILD for source -validation (makepkg -g >>PKGBUILD). -.TP -.B "\-h, \-\-help" -Output syntax and commandline options. -.TP -.B "\-i, \-\-install" -Install/Upgrade the package after a successful build. -.TP -.B "\-j <jobs>" -Sets MAKEFLAGS="-j<jobs>" before building the package. This is useful for overriding -the MAKEFLAGS setting in /etc/makepkg.conf. -.TP -.B "\-m, \-\-nocolor" -Disable color in output messages -.TP -.B "\-n, \-\-nostrip" -Do not strip binaries and libraries. -.TP -.B "\-o, \-\-nobuild" -Download and extract files only, do not build. -.TP -.B "\-p <buildscript>" -Read the package script \fI<buildscript>\fP instead of the default (\fIPKGBUILD\fP). -.TP -.B "\-r, \-\-rmdeps" -Upon successful build, remove any dependencies installed by makepkg/pacman during -dependency auto-resolution (using \fB-b\fP or \fB-s\fP). -.TP -.B "\-s, \-\-syncdeps" -Install missing dependencies using pacman. When makepkg finds missing build-time -or run-time dependencies, it will run pacman to try and resolve them. If successful, -pacman will download the missing packages from a package repository and -install them for you. -.TP -.B "\-S, \-\-sudosync" -Install missing dependencies using pacman and sudo. This is the same as \fB-s\fP -except that makepkg will call pacman with sudo. This means you don't have to -build as root to use dependency auto-resolution. -.TP -.B "\-w <destdir>" -Write the resulting package file to the directory \fI<destdir>\fP instead of the -current working directory. -.TP -.B "\-\-noconfirm" -When calling pacman to resolve dependencies or conflicts, makepkg can pass -the \fI--noconfirm\fP option to it so it does not wait for any user -input before proceeding with operations. -.TP -.B "\-\-noprogressbar" -When calling pacman, makepkg can pass the \fI--noprogressbar\fP option to it. -This is useful if one is directing makepkg's output to a non-terminal (ie, a file). - -.SH CONFIGURATION -Configuration options are stored in \fI/etc/makepkg.conf\fP. This file is parsed -as a bash script, so you can export any special compiler flags you wish -to use. This is helpful for building for different architectures, or with -different optimizations. - -\fBNOTE:\fP This does not guarantee that all package Makefiles will use -your exported variables. Some of them are flaky... -.SH SEE ALSO -\fBpacman\fP is the package manager that uses packages built by makepkg. - -See the Arch Linux Documentation for package-building guidelines if you wish -to contribute packages to the Arch Linux project. -.SH AUTHOR -.nf -Judd Vinet <jvinet(a)zeroflux.org> -.fi Index: pacman-lib/doc/pacman.8 diff -u /dev/null pacman-lib/doc/pacman.8:1.3 --- /dev/null Wed Feb 7 17:29:23 2007 +++ pacman-lib/doc/pacman.8 Wed Feb 7 17:29:21 2007 @@ -0,0 +1,334 @@ +.TH pacman 8 "January 21, 2006" "pacman @PACKAGE_VERSION@" "" +.SH NAME +pacman \- package manager utility +.SH SYNOPSIS +\fBpacman <operation> [options] <package> [package] ...\fP +.SH DESCRIPTION +\fBpacman\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 package are \fIgzipped 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 .tar.gz packages. See +\fBQUERY OPTIONS\fP below. +.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 -S qt\fP will download +qt and all the packages it depends on and install them. You could also use +\fBpacman -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 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 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 from a script. +.TP +.B "\-\-noprogressbar" +Do not show a progress bar when downloading files. This can be useful for +scripts that call pacman and capture the output. +.SH SYNC OPTIONS +.TP +.B "\-c, \-\-clean" +Remove old packages from the cache. When pacman 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 "\-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 matches <regexp>. +.TP +.B "\-u, \-\-sysupgrade" +Upgrades all packages that are out of date. pacman will examine every +package installed on the system, and if a newer package exists on the +server it will upgrade. pacman 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 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 explicitly installed (ie, not pulled in +as a dependency by other packages) and are not required by any other +packages. +.TP +.B "\-g, \-\-groups" +Display all package members of a named group, or all grouped packages if +no name is specified. +.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 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 matches <regexp>. +.SH HANDLING CONFIG FILES +pacman 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 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/passwd etc/group etc/shadow +NoUpgrade = etc/fstab + +Include = /etc/pacman.d/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. +.B "CacheDir = path/to/cache/dir" +Overrides the default location of the package cache directory. The default is +\fIvar/cache/pacman\fP. +.TP +.TP +.B "HoldPkg = <package> [package] ..." +If a user tries to \fB--remove\fP a package that's listed in HoldPkg, pacman +will ask for confirmation before proceeding. +.TP +.B "IgnorePkg = <package> [package] ..." +Instructs pacman to ignore any upgrades for this package when performing a +\fB--sysupgrade\fP. +.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 will use this proxy server for all ftp/http transfers. +.TP +.B "XferCommand = /path/to/command %u" +If set, pacman 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'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 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.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. +The order of repositories in the file matters; repositories listed first will +take precidence over those listed later in the file when packages in two +repositories have identical names, regardless of version number. +.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/var/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 /var/abs/local /home/pkgs/custom.db.tar.gz +.fi +.RE + +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 +\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 +.nf +Judd Vinet <jvinet(a)zeroflux.org> +.fi Index: pacman-lib/doc/pacman.8.in diff -u pacman-lib/doc/pacman.8.in:1.10 pacman-lib/doc/pacman.8.in:removed --- pacman-lib/doc/pacman.8.in:1.10 Thu Jan 25 20:57:06 2007 +++ pacman-lib/doc/pacman.8.in Wed Feb 7 17:29:23 2007 @@ -1,334 +0,0 @@ -.TH pacman 8 "January 21, 2006" "pacman @PACKAGE_VERSION@" "" -.SH NAME -pacman \- package manager utility -.SH SYNOPSIS -\fBpacman <operation> [options] <package> [package] ...\fP -.SH DESCRIPTION -\fBpacman\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 package are \fIgzipped 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 .tar.gz packages. See -\fBQUERY OPTIONS\fP below. -.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 -S qt\fP will download -qt and all the packages it depends on and install them. You could also use -\fBpacman -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 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 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 from a script. -.TP -.B "\-\-noprogressbar" -Do not show a progress bar when downloading files. This can be useful for -scripts that call pacman and capture the output. -.SH SYNC OPTIONS -.TP -.B "\-c, \-\-clean" -Remove old packages from the cache. When pacman 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 "\-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 matches <regexp>. -.TP -.B "\-u, \-\-sysupgrade" -Upgrades all packages that are out of date. pacman will examine every -package installed on the system, and if a newer package exists on the -server it will upgrade. pacman 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 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 explicitly installed (ie, not pulled in -as a dependency by other packages) and are not required by any other -packages. -.TP -.B "\-g, \-\-groups" -Display all package members of a named group, or all grouped packages if -no name is specified. -.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 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 matches <regexp>. -.SH HANDLING CONFIG FILES -pacman 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 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/passwd etc/group etc/shadow -NoUpgrade = etc/fstab - -Include = /etc/pacman.d/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. -.B "CacheDir = path/to/cache/dir" -Overrides the default location of the package cache directory. The default is -\fIvar/cache/pacman\fP. -.TP -.TP -.B "HoldPkg = <package> [package] ..." -If a user tries to \fB--remove\fP a package that's listed in HoldPkg, pacman -will ask for confirmation before proceeding. -.TP -.B "IgnorePkg = <package> [package] ..." -Instructs pacman to ignore any upgrades for this package when performing a -\fB--sysupgrade\fP. -.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 will use this proxy server for all ftp/http transfers. -.TP -.B "XferCommand = /path/to/command %u" -If set, pacman 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'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 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.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. -The order of repositories in the file matters; repositories listed first will -take precidence over those listed later in the file when packages in two -repositories have identical names, regardless of version number. -.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/var/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 /var/abs/local /home/pkgs/custom.db.tar.gz -.fi -.RE - -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 -\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 -.nf -Judd Vinet <jvinet(a)zeroflux.org> -.fi Index: pacman-lib/doc/po/.cvsignore diff -u pacman-lib/doc/po/.cvsignore:1.1 pacman-lib/doc/po/.cvsignore:removed --- pacman-lib/doc/po/.cvsignore:1.1 Tue Jan 16 22:40:08 2007 +++ pacman-lib/doc/po/.cvsignore Wed Feb 7 17:29:23 2007 @@ -1,6 +0,0 @@ -Makefile -Makefile.in -*.gmo -POTFILES -stamp-po - Index: pacman-lib/doc/po/hu.po diff -u pacman-lib/doc/po/hu.po:1.6 pacman-lib/doc/po/hu.po:removed --- pacman-lib/doc/po/hu.po:1.6 Tue Jan 30 02:47:19 2007 +++ pacman-lib/doc/po/hu.po Wed Feb 7 17:29:23 2007 @@ -1,2595 +0,0 @@ -# Hungarian translation of pacman. -# Copyright (C) 2006 Free Software Foundation, Inc. -# -msgid "" -msgstr "" -"Project-Id-Version: pacman\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2007-01-30 13:43-0600\n" -"PO-Revision-Date: 2006-08-26 14:53+0200\n" -"Last-Translator: Hungarian <frugalware-devel(a)frugalware.org>\n" -"Language-Team: Hungarian <frugalware-devel(a)frugalware.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=ISO-8859-2\n" -"Content-Transfer-Encoding: 8bit\n" - -# type: TH -#: pacman.8:1 -#, no-wrap -msgid "pacman" -msgstr "" - -# type: TH -#: pacman.8:1 -#, no-wrap -msgid "January 21, 2006" -msgstr "2006. január 21." - -# type: TH -#: pacman.8:1 -#, no-wrap -msgid "pacman 3.0.0" -msgstr "" - -# type: SH -#: pacman.8:2 makepkg.8:2 PKGBUILD.8:2 -#, no-wrap -msgid "NAME" -msgstr "NÉV" - -# type: Plain text -#: pacman.8:4 -msgid "pacman - package manager utility" -msgstr "pacman - csomagkezelõ segédeszköz" - -# type: SH -#: pacman.8:4 makepkg.8:4 -#, no-wrap -msgid "SYNOPSIS" -msgstr "ÁTTEKINTÉS" - -# type: Plain text -#: pacman.8:6 -msgid "B<pacman E<lt>operationE<gt> [options] E<lt>packageE<gt> [package] ...>" -msgstr "B<pacman E<lt>mûveletE<gt> [opciók] E<lt>csomagE<gt> [csomag] ...>" - -# type: SH -#: pacman.8:6 makepkg.8:6 PKGBUILD.8:4 -#, no-wrap -msgid "DESCRIPTION" -msgstr "LEÍRÁS" - -# type: Plain text -#: pacman.8:11 -msgid "" -"B<pacman> is a I<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 package are I<gzipped tar> format." -msgstr "" - -# type: SH -#: pacman.8:11 -#, no-wrap -msgid "OPERATIONS" -msgstr "MÛVELETEK" - -# type: TP -#: pacman.8:12 -#, no-wrap -msgid "B<-A, --add>" -msgstr "B<-A, --add>" - -# type: Plain text -#: pacman.8:16 -msgid "" -"Add a package to the system. Package will be uncompressed into the " -"installation root and the database will be updated." -msgstr "" - -# type: TP -#: pacman.8:16 -#, no-wrap -msgid "B<-F, --freshen>" -msgstr "B<-F, --freshen>" - -# type: Plain text -#: pacman.8:20 -msgid "" -"This is like --upgrade except that, unlike --upgrade, this will only upgrade " -"packages that are already installed on your system." -msgstr "" - -# type: TP -#: pacman.8:20 -#, no-wrap -msgid "B<-Q, --query>" -msgstr "B<-Q, --query>" - -# type: Plain text -#: pacman.8:28 -msgid "" -"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 .tar.gz " -"packages. See B<QUERY OPTIONS> below." -msgstr "" - -# type: TP -#: pacman.8:28 -#, no-wrap -msgid "B<-R, --remove>" -msgstr "B<-R, --remove>" - -# type: Plain text -#: pacman.8:35 -msgid "" -"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 I<.pacsave> extension unless the B<--nosave> option was " -"used." -msgstr "" - -# type: TP -#: pacman.8:35 -#, no-wrap -msgid "B<-S, --sync>" -msgstr "B<-S, --sync>" - -# type: Plain text -#: pacman.8:42 -msgid "" -"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, B<pacman -S qt> will download qt and all the " -"packages it depends on and install them. You could also use B<pacman -Su> to " -"upgrade all packages that are out of date (see below)." -msgstr "" - -# type: TP -#: pacman.8:42 -#, no-wrap -msgid "B<-U, --upgrade>" -msgstr "B<-U, --upgrade>" - -# type: Plain text -#: pacman.8:47 -msgid "" -"Upgrade a package. This is essentially a \"remove-then-add\" process. See " -"B<HANDLING CONFIG FILES> for an explanation on how pacman takes care of " -"config files." -msgstr "" - -# type: TP -#: pacman.8:47 -#, no-wrap -msgid "B<-V, --version>" -msgstr "B<-V, --version>" - -# type: Plain text -#: pacman.8:50 -msgid "Display version and exit." -msgstr "" - -# type: TP -#: pacman.8:50 makepkg.8:388 -#, no-wrap -msgid "B<-h, --help>" -msgstr "" - -# type: Plain text -#: pacman.8:54 -msgid "" -"Display syntax for the given operation. If no operation was supplied then " -"the general syntax is shown." -msgstr "" - -# type: SH -#: pacman.8:54 -#, no-wrap -msgid "OPTIONS" -msgstr "OPCIÓK" - -# type: TP -#: pacman.8:55 makepkg.8:368 -#, no-wrap -msgid "B<-d, --nodeps>" -msgstr "" - -# type: Plain text -#: pacman.8:61 -msgid "" -"Skips all dependency checks. Normally, pacman 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." -msgstr "" - -# type: TP -#: pacman.8:61 makepkg.8:378 -#, no-wrap -msgid "B<-f, --force>" -msgstr "" - -# type: Plain text -#: pacman.8:67 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:67 -#, no-wrap -msgid "B<-r, --root E<lt>pathE<gt>>" -msgstr "B<-r, --root E<lt>útvonalE<gt>>" - -# type: Plain text -#: pacman.8:76 -msgid "" -"Specify alternative installation root (default is \"/\"). This should I<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." -msgstr "" - -# type: TP -#: pacman.8:76 -#, no-wrap -msgid "B<-v, --verbose>" -msgstr "B<-v, --verbose>" - -# type: Plain text -#: pacman.8:79 -msgid "Output more status and error messages." -msgstr "" - -# type: TP -#: pacman.8:79 -#, no-wrap -msgid "B<--config E<lt>pathE<gt>>" -msgstr "B<--config E<lt>útvonalE<gt>>" - -# type: Plain text -#: pacman.8:82 -msgid "Specify an alternate configuration file." -msgstr "" - -# type: TP -#: pacman.8:82 makepkg.8:429 -#, no-wrap -msgid "B<--noconfirm>" -msgstr "" - -# type: Plain text -#: pacman.8:86 -msgid "" -"Bypass any and all \"Are you sure?\" messages. It's not a good idea to do " -"this unless you want to run pacman from a script." -msgstr "" - -# type: TP -#: pacman.8:86 makepkg.8:434 -#, no-wrap -msgid "B<--noprogressbar>" -msgstr "" - -# type: Plain text -#: pacman.8:90 -msgid "" -"Do not show a progress bar when downloading files. This can be useful for " -"scripts that call pacman and capture the output." -msgstr "" - -# type: SH -#: pacman.8:90 -#, no-wrap -msgid "SYNC OPTIONS" -msgstr "" - -# type: TP -#: pacman.8:91 makepkg.8:362 -#, no-wrap -msgid "B<-c, --clean>" -msgstr "" - -# type: Plain text -#: pacman.8:98 -msgid "" -"Remove old packages from the cache. When pacman downloads packages, it " -"saves them in I</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 I<old> packages. Use it twice to " -"remove I<all> packages from the cache." -msgstr "" - -# type: TP -#: pacman.8:98 pacman.8:168 -#, no-wrap -msgid "B<-g, --groups>" -msgstr "B<-g, --groups>" - -# type: Plain text -#: pacman.8:102 -msgid "" -"Display all the members for each package group specified. If no group names " -"are provided, all groups will be listed." -msgstr "" - -# type: TP -#: pacman.8:102 pacman.8:172 -#, no-wrap -msgid "B<-i, --info>" -msgstr "B<-i, --info>" - -# type: Plain text -#: pacman.8:107 -msgid "" -"Display dependency information for a given package. This will search " -"through all repositories for a matching package and display the " -"dependencies, conflicts, etc." -msgstr "" - -# type: TP -#: pacman.8:107 pacman.8:176 -#, no-wrap -msgid "B<-l, --list>" -msgstr "B<-l, --list>" - -# type: Plain text -#: pacman.8:111 -msgid "" -"List all files in the specified repositories. Multiple repositories can be " -"specified on the command line." -msgstr "" - -# type: TP -#: pacman.8:111 -#, no-wrap -msgid "B<-p, --print-uris>" -msgstr "B<-p, --print-uris>" - -# type: Plain text -#: pacman.8:116 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:116 pacman.8:192 -#, no-wrap -msgid "B<-s, --search E<lt>regexpE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:120 -msgid "" -"This will search each package in the package list for names or descriptions " -"that matches E<lt>regexpE<gt>." -msgstr "" - -# type: TP -#: pacman.8:120 -#, no-wrap -msgid "B<-u, --sysupgrade>" -msgstr "B<-u, --sysupgrade>" - -# type: Plain text -#: pacman.8:128 -msgid "" -"Upgrades all packages that are out of date. pacman will examine every " -"package installed on the system, and if a newer package exists on the server " -"it will upgrade. pacman 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." -msgstr "" - -# type: TP -#: pacman.8:128 -#, no-wrap -msgid "B<-w, --downloadonly>" -msgstr "B<-w, --downloadonly>" - -# type: Plain text -#: pacman.8:131 -msgid "" -"Retrieve all packages from the server, but do not install/upgrade anything." -msgstr "" - -# type: TP -#: pacman.8:131 -#, no-wrap -msgid "B<-y, --refresh>" -msgstr "B<-y, --refresh>" - -# type: Plain text -#: pacman.8:136 -msgid "" -"Download a fresh copy of the master package list from the ftp server defined " -"in I</etc/pacman.conf>. This should typically be used each time you use B<--" -"sysupgrade>." -msgstr "" - -# type: TP -#: pacman.8:136 -#, no-wrap -msgid "B<--ignore E<lt>pkgE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:141 -msgid "" -"This option functions exactly the same as the B<IgnorePkg> configuration " -"directive. Sometimes it can be handy to skip some package updates without " -"having to edit I<pacman.conf> each time." -msgstr "" - -# type: SH -#: pacman.8:141 -#, no-wrap -msgid "REMOVE OPTIONS" -msgstr "ELTÁVOLÍTÁSI OPCIÓK" - -# type: TP -#: pacman.8:142 -#, no-wrap -msgid "B<-c, --cascade>" -msgstr "B<-c, --cascade>" - -# type: Plain text -#: pacman.8:146 -msgid "" -"Remove all target packages, as well as all packages that depend on one or " -"more target packages. This operation is recursive." -msgstr "" - -# type: TP -#: pacman.8:146 -#, no-wrap -msgid "B<-k, --keep>" -msgstr "B<-k, --keep>" - -# type: Plain text -#: pacman.8:149 -msgid "Removes the database entry only. Leaves all files in place." -msgstr "" - -# type: TP -#: pacman.8:149 -#, no-wrap -msgid "B<-n, --nosave>" -msgstr "B<-n, --nosave>" - -# type: Plain text -#: pacman.8:156 -msgid "" -"Instructs pacman to ignore file backup designations. Normally, when a file " -"is about to be I<removed> from the system the database is first checked to " -"see if the file should be renamed to a .pacsave extension. If B<--nosave> " -"is used, these designations are ignored and the files are removed." -msgstr "" - -# type: TP -#: pacman.8:156 -#, no-wrap -msgid "B<-s, --recursive>" -msgstr "B<-s, --recursive>" - -# type: Plain text -#: pacman.8:162 -msgid "" -"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." -msgstr "" - -# type: SH -#: pacman.8:162 -#, no-wrap -msgid "QUERY OPTIONS" -msgstr "LEKÉRDEZÉSI OPCIÓK" - -# type: TP -#: pacman.8:163 -#, no-wrap -msgid "B<-e, --orphans>" -msgstr "B<-e, --orphans>" - -# type: Plain text -#: pacman.8:168 -msgid "" -"List all packages that were explicitly installed (ie, not pulled in as a " -"dependency by other packages) and are not required by any other packages." -msgstr "" - -# type: Plain text -#: pacman.8:172 -msgid "" -"Display all package members of a named group, or all grouped packages if no " -"name is specified." -msgstr "" - -# type: Plain text -#: pacman.8:176 -msgid "" -"Display information on a given package. If it is used with the B<-p> option " -"then the .PKGINFO file will be printed." -msgstr "" - -# type: Plain text -#: pacman.8:180 -msgid "" -"List all files owned by E<lt>packageE<gt>. Multiple packages can be " -"specified on the command line." -msgstr "" - -# type: TP -#: pacman.8:180 -#, no-wrap -msgid "B<-m, --foreign>" -msgstr "" - -# type: Plain text -#: pacman.8:184 -msgid "" -"List all packages that were not found in the sync database(s). Typically " -"these are packages that were downloaded manually and installed with --add." -msgstr "" - -# type: TP -#: pacman.8:184 -#, no-wrap -msgid "B<-o, --owns E<lt>fileE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:187 -msgid "Search for the package that owns E<lt>fileE<gt>." -msgstr "" - -# type: TP -#: pacman.8:187 -#, no-wrap -msgid "B<-p, --file>" -msgstr "" - -# type: Plain text -#: pacman.8:192 -msgid "" -"Tells pacman 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 B<--info> and B<--list>." -msgstr "" - -# type: Plain text -#: pacman.8:196 -msgid "" -"This will search each locally-installed package for names or descriptions " -"that matches E<lt>regexpE<gt>." -msgstr "" - -# type: SH -#: pacman.8:196 -#, no-wrap -msgid "HANDLING CONFIG FILES" -msgstr "" - -# type: Plain text -#: pacman.8:203 -msgid "" -"pacman 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:" -msgstr "" - -# type: TP -#: pacman.8:203 -#, no-wrap -msgid "original=B<X>, current=B<X>, new=B<X>" -msgstr "" - -# type: Plain text -#: pacman.8:206 -msgid "" -"All three files are the same, so we win either way. Install the new file." -msgstr "" - -# type: TP -#: pacman.8:206 -#, no-wrap -msgid "original=B<X>, current=B<X>, new=B<Y>" -msgstr "" - -# type: Plain text -#: pacman.8:211 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:211 -#, no-wrap -msgid "original=B<X>, current=B<Y>, new=B<X>" -msgstr "" - -# type: Plain text -#: pacman.8:216 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:216 -#, no-wrap -msgid "original=B<X>, current=B<Y>, new=B<Y>" -msgstr "" - -# type: Plain text -#: pacman.8:219 -msgid "" -"The new one is identical to the current one. Win win. Install the new file." -msgstr "" - -# type: TP -#: pacman.8:219 -#, no-wrap -msgid "original=B<X>, current=B<Y>, new=B<Z>" -msgstr "" - -# type: Plain text -#: pacman.8:224 -msgid "" -"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." -msgstr "" - -# type: SH -#: pacman.8:224 makepkg.8:439 -#, no-wrap -msgid "CONFIGURATION" -msgstr "" - -# type: Plain text -#: pacman.8:230 -msgid "" -"pacman will attempt to read I</etc/pacman.conf> each time it is invoked. " -"This configuration file is divided into sections or I<repositories>. Each " -"section defines a package repository that pacman can use when searching for " -"packages in --sync mode. The exception to this is the I<options> section, " -"which defines global options." -msgstr "" - -# type: SH -#: pacman.8:231 -#, no-wrap -msgid "Example:" -msgstr "" - -# type: Plain text -#: pacman.8:237 -#, no-wrap -msgid "" -"[options]\n" -"NoUpgrade = etc/passwd etc/group etc/shadow\n" -"NoUpgrade = etc/fstab\n" -msgstr "" - -# type: Plain text -#: pacman.8:239 -#, no-wrap -msgid "Include = /etc/pacman.d/current\n" -msgstr "" - -# type: Plain text -#: pacman.8:242 -#, no-wrap -msgid "" -"[custom]\n" -"Server = file:///home/pkgs\n" -msgstr "" - -# type: SH -#: pacman.8:245 -#, no-wrap -msgid "CONFIG: OPTIONS" -msgstr "" - -# type: TP -#: pacman.8:246 -#, no-wrap -msgid "B<DBPath = path/to/db/dir>" -msgstr "" - -# type: Plain text -#: pacman.8:253 -msgid "" -"Overrides the default location of the toplevel database directory. The " -"default is I<var/lib/pacman>. B<CacheDir = path/to/cache/dir> Overrides the " -"default location of the package cache directory. The default is I<var/cache/" -"pacman>." -msgstr "" - -# type: TP -#: pacman.8:254 -#, no-wrap -msgid "B<HoldPkg = E<lt>packageE<gt> [package] ...>" -msgstr "" - -# type: Plain text -#: pacman.8:258 -msgid "" -"If a user tries to B<--remove> a package that's listed in HoldPkg, pacman " -"will ask for confirmation before proceeding." -msgstr "" - -# type: TP -#: pacman.8:258 -#, no-wrap -msgid "B<IgnorePkg = E<lt>packageE<gt> [package] ...>" -msgstr "" - -# type: Plain text -#: pacman.8:262 -msgid "" -"Instructs pacman to ignore any upgrades for this package when performing a " -"B<--sysupgrade>." -msgstr "" - -# type: TP -#: pacman.8:262 -#, no-wrap -msgid "B<Include = E<lt>pathE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:266 -msgid "" -"Include another config file. This config file can include repositories or " -"general configuration options." -msgstr "" - -# type: TP -#: pacman.8:266 -#, no-wrap -msgid "B<ProxyServer = E<lt>host|ipE<gt>[:port]>" -msgstr "" - -# type: Plain text -#: pacman.8:269 -msgid "If set, pacman will use this proxy server for all ftp/http transfers." -msgstr "" - -# type: TP -#: pacman.8:269 -#, no-wrap -msgid "B<XferCommand = /path/to/command %u>" -msgstr "" - -# type: Plain text -#: pacman.8:275 -msgid "" -"If set, pacman will use this external program to download all remote files. " -"All instances of B<%u> will be replaced with the URL to be downloaded. If " -"present, instances of B<%o> will be replaced with the local filename, plus a " -"\".part\" extension, which allows programs like wget to do file resumes " -"properly." -msgstr "" - -# type: Plain text -#: pacman.8:279 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:279 -#, no-wrap -msgid "B<NoPassiveFtp>" -msgstr "" - -# type: Plain text -#: pacman.8:282 -msgid "" -"Disables passive ftp connections when downloading packages. (aka Active Mode)" -msgstr "" - -# type: TP -#: pacman.8:282 -#, no-wrap -msgid "B<NoUpgrade = E<lt>fileE<gt> [file] ...>" -msgstr "" - -# type: Plain text -#: pacman.8:286 -msgid "" -"All files listed with a B<NoUpgrade> directive will never be touched during " -"a package install/upgrade. I<Note:> do not include the leading slash when " -"specifying files." -msgstr "" - -# type: TP -#: pacman.8:286 -#, no-wrap -msgid "B<NoExtract = E<lt>fileE<gt> [file] ...>" -msgstr "" - -# type: Plain text -#: pacman.8:293 -msgid "" -"All files listed with a B<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." -msgstr "" - -# type: TP -#: pacman.8:293 -#, no-wrap -msgid "B<UseSyslog>" -msgstr "" - -# type: Plain text -#: pacman.8:297 -msgid "" -"Log action messages through syslog(). This will insert pacman log entries " -"into your /var/log/messages or equivalent." -msgstr "" - -# type: TP -#: pacman.8:297 -#, no-wrap -msgid "B<LogFile = /path/to/file>" -msgstr "" - -# type: Plain text -#: pacman.8:300 -msgid "Log actions directly to a file, usually /var/log/pacman.log." -msgstr "" - -# type: SH -#: pacman.8:301 -#, no-wrap -msgid "CONFIG: REPOSITORIES" -msgstr "" - -# type: Plain text -#: pacman.8:311 -msgid "" -"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 I<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. The order of repositories in the file matters; " -"repositories listed first will take precidence over those listed later in " -"the file when packages in two repositories have identical names, regardless " -"of version number." -msgstr "" - -# type: SH -#: pacman.8:311 -#, no-wrap -msgid "USING YOUR OWN REPOSITORY" -msgstr "" - -# type: Plain text -#: pacman.8:315 -msgid "" -"Let's say you have a bunch of custom packages in I</home/pkgs> and their " -"respective PKGBUILD files are all in I</var/abs/local>. All you need to do " -"is generate a compressed package database in the I</home/pkgs> directory so " -"pacman can find it when run with --refresh." -msgstr "" - -# type: Plain text -#: pacman.8:319 -#, no-wrap -msgid "# gensync /var/abs/local /home/pkgs/custom.db.tar.gz\n" -msgstr "" - -# type: Plain text -#: pacman.8:329 -msgid "" -"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 I<{treename}.db.tar.gz>, where " -"{treename} is the name of the section defined in the configuration file. " -"That's it! Now configure your I<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." -msgstr "" - -# type: SH -#: pacman.8:329 makepkg.8:447 PKGBUILD.8:453 -#, no-wrap -msgid "SEE ALSO" -msgstr "LÁSD MÉG" - -# type: Plain text -#: pacman.8:331 -msgid "B<makepkg> is the package-building tool that comes with pacman." -msgstr "" - -# type: SH -#: pacman.8:331 makepkg.8:452 PKGBUILD.8:456 -#, no-wrap -msgid "AUTHOR" -msgstr "SZERZÕ" - -# type: Plain text -#: pacman.8:334 makepkg.8:455 -#, no-wrap -msgid "Judd Vinet E<lt>jvinet(a)zeroflux.orgE<gt>\n" -msgstr "" - -# type: TH -#: makepkg.8:1 -#, no-wrap -msgid "makepkg" -msgstr "makepkg" - -# type: TH -#: makepkg.8:1 -#, no-wrap -msgid "January 30, 2006" -msgstr "2006. január 30." - -# type: TH -#: makepkg.8:1 -#, no-wrap -msgid "makepkg #VERSION#" -msgstr "" - -# type: Plain text -#: makepkg.8:4 -msgid "makepkg - package build utility" -msgstr "makepkg - csomagkészítõ segédeszköz" - -# type: Plain text -#: makepkg.8:6 -msgid "B<makepkg [options]>" -msgstr "B<makepkg [opciók]>" - -# type: Plain text -#: makepkg.8:15 -msgid "" -"B<makepkg> will build packages for you. All it needs is a build-capable " -"linux platform, wget, and some build scripts. The advantage to a script-" -"based build is that you only really do the work once. Once you have the " -"build script for a package, you just need to run makepkg and it will do the " -"rest: download and validate source files, check dependencies, configure the " -"buildtime settings, build the package, install the package into a temporary " -"root, make customizations, generate meta-info, and package the whole thing " -"up for B<pacman> to use." -msgstr "" - -# type: Plain text -#: makepkg.8:18 -msgid "" -"B<makeworld> can be used to rebuild an entire package group or the entire " -"build tree. See B<makeworld --help> for syntax." -msgstr "" - -# type: SH -#: makepkg.8:18 -#, no-wrap -msgid "BUILD PROCESS (or How To Build Your Own Packages)" -msgstr "" - -# type: Plain text -#: makepkg.8:22 -msgid "" -"Start in an isolated directory (ie, it's not used for anything other than " -"building this package). The build script should be called PKGBUILD and it " -"should bear resemblance to the example below." -msgstr "" - -# type: Plain text -#: makepkg.8:27 -msgid "" -"B<NOTE:> If you have a local copy of the Arch Build System (ABS) tree on " -"your computer, you can copy the PKGBUILD.proto file to your new package " -"build directory and edit it from there. To acquire/sync the ABS tree, use " -"the B<abs> script included with pacman/makepkg." -msgstr "" - -# type: SH -#: makepkg.8:30 PKGBUILD.8:11 -#, no-wrap -msgid "PKGBUILD Example:" -msgstr "" - -# type: Plain text -#: makepkg.8:45 -#, no-wrap -msgid "" -"pkgname=modutils\n" -"pkgver=2.4.25\n" -"pkgrel=1\n" -"pkgdesc=\"Utilities for inserting and removing modules from the linux kernel\"\n" -"url=\"http://www.kernel.org\"\n" -"backup=(etc/modules.conf)\n" -"makedepends=('bash' 'mawk')\n" -"depends=('glibc' 'zlib')\n" -"source=(ftp://ftp.kernel.org/pub/linux/utils/kernel/$pkgname/v2.4/$pkgname-… \\e\n" -" modules.conf)\n" -"md5sums=('2c0cca3ef6330a187c6ef4fe41ecaa4d' \\e\n" -" '35175bee593a7cc7d6205584a94d8625')\n" -msgstr "" - -# type: Plain text -#: makepkg.8:55 -#, no-wrap -msgid "" -"build() {\n" -" cd $startdir/src/$pkgname-$pkgver\n" -" ./configure --prefix=/usr --enable-insmod-static\n" -" make || return 1\n" -" make prefix=$startdir/pkg/usr install\n" -" mv $startdir/pkg/usr/sbin $startdir/pkg\n" -" mkdir -p $startdir/pkg/etc\n" -" cp ../modules.conf $startdir/pkg/etc\n" -"}\n" -msgstr "" -"build() {\n" -" cd $startdir/src/$pkgname-$pkgver\n" -" ./configure --prefix=/usr --enable-insmod-static\n" -" make || return 1\n" -" make prefix=$startdir/pkg/usr install\n" -" mv $startdir/pkg/usr/sbin $startdir/pkg\n" -" mkdir -p $startdir/pkg/etc\n" -" cp ../modules.conf $startdir/pkg/etc\n" -"}\n" - -# type: Plain text -#: makepkg.8:63 -msgid "" -"As you can see, the setup is fairly simple. The first three lines define " -"the package name and version info. They also define the final package name " -"which will be of the form I<$pkgname-$pkgver-$pkgrel.pkg.tar.gz>. The " -"fourth line provides a brief description of the package. These four lines " -"should be present in every PKGBUILD script." -msgstr "" - -# type: Plain text -#: makepkg.8:67 -msgid "" -"The line with I<backup=> specifies files that should be treated specially " -"when removing or upgrading packages. See B<HANDLING CONFIG FILES> in the " -"I<pacman> manpage for more information on this." -msgstr "" - -# type: Plain text -#: makepkg.8:73 -msgid "" -"Lines 7 and 8 list the dependencies for this package. The I<depends> array " -"specifies the run-time dependencies and I<makedepends> specifies the build-" -"time dependencies. In order to run the package, I<depends> must be " -"satisfied. To build the package, B<all> dependencies must be satisifed " -"first. makepkg will check this before attempting to build the package." -msgstr "" - -# type: Plain text -#: makepkg.8:77 -msgid "" -"The I<source> array tells makepkg which files to download/extract before " -"compiling begins. The I<md5sums> array provides md5sums for each of these " -"files. These are used to validate the integrity of the source files." -msgstr "" - -# type: Plain text -#: makepkg.8:82 -msgid "" -"Once your PKGBUILD is created, you can run I<makepkg> from the build " -"directory. makepkg will then check dependencies and look for the source " -"files required to build. If some are missing it will attempt to download " -"them, provided there is a fully-qualified URL in the I<source> array." -msgstr "" - -# type: Plain text -#: makepkg.8:87 -msgid "" -"The sources are then extracted into a directory called ./src and the " -"I<build> function is called. This is where all package configuration, " -"building, and installing should be done. Any customization will likely take " -"place here." -msgstr "" - -# type: Plain text -#: makepkg.8:91 -msgid "" -"After a package is built, the I<build> function must install the package " -"files into a special package root, which can be referenced by B<$startdir/" -"pkg> in the I<build> function. The typical way to do this is one of the " -"following:" -msgstr "" - -# type: Plain text -#: makepkg.8:95 -#, no-wrap -msgid "make DESTDIR=$startdir/pkg install\n" -msgstr "make DESTDIR=$startdir/pkg install\n" - -# type: Plain text -#: makepkg.8:97 -#, no-wrap -msgid "or\n" -msgstr "vagy\n" - -# type: Plain text -#: makepkg.8:99 -#, no-wrap -msgid "make prefix=$startdir/pkg/usr install\n" -msgstr "make prefix=$startdir/pkg/usr install\n" - -# type: Plain text -#: makepkg.8:105 -msgid "" -"Notice that the \"/usr\" portion should be present with \"prefix\", but not " -"\"DESTDIR\". \"DESTDIR\" is the favorable option to use, but not all " -"Makefiles support it. Use \"prefix\" only when \"DESTDIR\" is unavailable." -msgstr "" - -# type: Plain text -#: makepkg.8:112 -msgid "" -"Once the package is successfully installed into the package root, I<makepkg> " -"will remove some directories (as per Arch Linux package guidelines; if you " -"use this elsewhere, feel free to change it) like /usr/doc and /usr/info. It " -"will then strip debugging info from libraries and binaries and generate a " -"meta-info file. Finally, it will compress everything into a .pkg.tar.gz " -"file and leave it in the directory you ran B<makepkg> from." -msgstr "" - -# type: Plain text -#: makepkg.8:115 -msgid "" -"At this point you should have a package file in the current directory, named " -"something like name-version-release.pkg.tar.gz. Done!" -msgstr "" - -# type: SH -#: makepkg.8:116 PKGBUILD.8:121 -#, no-wrap -msgid "Install/Upgrade/Remove Scripting" -msgstr "" - -# type: Plain text -#: makepkg.8:120 PKGBUILD.8:125 -msgid "" -"Pacman has the ability to store and execute a package-specific script when " -"it installs, removes, or upgrades a package. This allows a package to " -"\"configure itself\" after installation and do the opposite right before it " -"is removed." -msgstr "" - -# type: Plain text -#: makepkg.8:122 PKGBUILD.8:127 -msgid "The exact time the script is run varies with each operation:" -msgstr "" - -# type: TP -#: makepkg.8:122 PKGBUILD.8:127 -#, no-wrap -msgid "B<pre_install>" -msgstr "" - -# type: Plain text -#: makepkg.8:125 makepkg.8:133 PKGBUILD.8:130 PKGBUILD.8:138 -msgid "script is run right before files are extracted." -msgstr "" - -# type: TP -#: makepkg.8:126 PKGBUILD.8:131 -#, no-wrap -msgid "B<post_install>" -msgstr "" - -# type: Plain text -#: makepkg.8:129 PKGBUILD.8:134 -msgid "script is run right after files are extracted." -msgstr "" - -# type: TP -#: makepkg.8:130 PKGBUILD.8:135 -#, no-wrap -msgid "B<pre_upgrade>" -msgstr "" - -# type: TP -#: makepkg.8:134 PKGBUILD.8:139 -#, no-wrap -msgid "B<post_upgrade>" -msgstr "" - -# type: Plain text -#: makepkg.8:137 PKGBUILD.8:142 -msgid "script is run after files are extracted." -msgstr "" - -# type: TP -#: makepkg.8:138 PKGBUILD.8:143 -#, no-wrap -msgid "B<pre_remove>" -msgstr "" - -# type: Plain text -#: makepkg.8:141 PKGBUILD.8:146 -msgid "script is run right before files are removed." -msgstr "" - -# type: TP -#: makepkg.8:142 PKGBUILD.8:147 -#, no-wrap -msgid "B<post_remove>" -msgstr "" - -# type: Plain text -#: makepkg.8:145 PKGBUILD.8:150 -msgid "script is run right after files are removed." -msgstr "" - -# type: Plain text -#: makepkg.8:149 PKGBUILD.8:154 -msgid "" -"To use this feature, just create a file (eg, pkgname.install) and put it in " -"the same directory as the PKGBUILD script. Then use the I<install> " -"directive:" -msgstr "" - -# type: Plain text -#: makepkg.8:152 PKGBUILD.8:157 -#, no-wrap -msgid "install=pkgname.install\n" -msgstr "" - -# type: Plain text -#: makepkg.8:156 -msgid "" -"The install script does not need to be specified in the I<source> array." -msgstr "" - -# type: SH -#: makepkg.8:159 -#, no-wrap -msgid "Install scripts must follow this format:" -msgstr "" - -# type: Plain text -#: makepkg.8:169 -#, no-wrap -msgid "" -"# arg 1: the new package version\n" -"pre_install() {\n" -" #\n" -" # do pre-install stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:177 -#, no-wrap -msgid "" -"# arg 1: the new package version\n" -"post_install() {\n" -" #\n" -" # do post-install stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:186 -#, no-wrap -msgid "" -"# arg 1: the new package version\n" -"# arg 2: the old package version\n" -"pre_upgrade() {\n" -" #\n" -" # do pre-upgrade stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:195 -#, no-wrap -msgid "" -"# arg 1: the new package version\n" -"# arg 2: the old package version\n" -"post_upgrade() {\n" -" #\n" -" # do post-upgrade stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:203 -#, no-wrap -msgid "" -"# arg 1: the old package version\n" -"pre_remove() {\n" -" #\n" -" # do pre-remove stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:211 -#, no-wrap -msgid "" -"# arg 1: the old package version\n" -"post_remove() {\n" -" #\n" -" # do post-remove stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:215 -#, no-wrap -msgid "" -"op=$1\n" -"shift\n" -"$op $*\n" -msgstr "" - -# type: Plain text -#: makepkg.8:219 -msgid "" -"This template is also available in your ABS tree (/var/abs/install.proto)." -msgstr "" - -# type: SH -#: makepkg.8:220 PKGBUILD.8:179 -#, no-wrap -msgid "PKGBUILD Directives" -msgstr "" - -# type: TP -#: makepkg.8:221 PKGBUILD.8:180 -#, no-wrap -msgid "B<pkgname>" -msgstr "" - -# type: Plain text -#: makepkg.8:225 PKGBUILD.8:184 -msgid "" -"The name of the package. This has be a unix-friendly name as it will be " -"used in the package filename." -msgstr "" - -# type: TP -#: makepkg.8:226 PKGBUILD.8:185 -#, no-wrap -msgid "B<pkgver>" -msgstr "" - -# type: Plain text -#: makepkg.8:229 PKGBUILD.8:188 -msgid "" -"This is the version of the software as released from the author (eg, 2.7.1)." -msgstr "" - -# type: TP -#: makepkg.8:230 PKGBUILD.8:189 -#, no-wrap -msgid "B<pkgrel>" -msgstr "" - -# type: Plain text -#: makepkg.8:233 -msgid "This is the release number specific to Arch Linux packages." -msgstr "" - -# type: TP -#: makepkg.8:234 PKGBUILD.8:193 -#, no-wrap -msgid "B<pkgdesc>" -msgstr "" - -# type: Plain text -#: makepkg.8:237 PKGBUILD.8:196 -msgid "" -"This should be a brief description of the package and its functionality." -msgstr "" - -# type: Plain text -#: makepkg.8:238 -#, fuzzy, no-wrap -msgid "B<options>" -msgstr "B<makepkg [opciók]>" - -# type: Plain text -#: makepkg.8:243 -msgid "" -"This array allows you to override some of makepkg's default behaviour when " -"building packages. To set an option, just include the option name in the " -"B<options> array." -msgstr "" - -# type: Plain text -#: makepkg.8:246 -msgid "I<Available Options:>" -msgstr "" - -# type: TP -#: makepkg.8:247 -#, no-wrap -msgid "B<FORCE>" -msgstr "" - -# type: Plain text -#: makepkg.8:251 -msgid "" -"force the package to be upgraded by B<--sysupgrade>, even if its an older " -"version." -msgstr "" - -# type: TP -#: makepkg.8:251 -#, no-wrap -msgid "B<KEEPDOCS>" -msgstr "" - -# type: Plain text -#: makepkg.8:254 -msgid "do not remove /usr/share/doc and /usr/share/info directories." -msgstr "" - -# type: TP -#: makepkg.8:254 -#, no-wrap -msgid "B<NOSTRIP>" -msgstr "" - -# type: Plain text -#: makepkg.8:257 -msgid "do not strip debugging symbols from binaries and libraries." -msgstr "" - -# type: TP -#: makepkg.8:260 PKGBUILD.8:204 -#, no-wrap -msgid "B<url>" -msgstr "" - -# type: Plain text -#: makepkg.8:264 PKGBUILD.8:208 -msgid "" -"This field contains an optional URL that is associated with the piece of " -"software being packaged. This is typically the project's website." -msgstr "" - -# type: TP -#: makepkg.8:265 PKGBUILD.8:209 -#, no-wrap -msgid "B<license>" -msgstr "" - -# type: Plain text -#: makepkg.8:275 -msgid "" -"This field specifies the license(s) that apply to the package. Commonly-" -"used licenses are typically found in I</usr/share/licenses/common>. If you " -"see the package's license there, simply reference it in the license field " -"(eg, B<license=\"GPL\">). If the package provides a license not found in I</" -"usr/share/licenses/common>, then you should include the license in the " -"package itself and set B<license=\"custom\"> or B<license=\"custom:" -"LicenseName\">. The license itself should be placed in a directory called I<" -"$startdir/pkg/usr/share/licenses/$pkgname>." -msgstr "" - -# type: Plain text -#: makepkg.8:278 -msgid "" -"If multiple licenses are applied, use the array form: B<license=('GPL' 'FDL')" -">" -msgstr "" - -# type: TP -#: makepkg.8:279 PKGBUILD.8:214 -#, no-wrap -msgid "B<install>" -msgstr "" - -# type: Plain text -#: makepkg.8:285 PKGBUILD.8:220 -msgid "" -"Specifies a special install script that is to be included in the package. " -"This file should reside in the same directory as the PKGBUILD, and will be " -"copied into the package by makepkg. It does not need to be included in the " -"I<source> array. (eg, install=modutils.install)" -msgstr "" - -# type: TP -#: makepkg.8:286 PKGBUILD.8:227 -#, no-wrap -msgid "B<source >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:293 PKGBUILD.8:234 -msgid "" -"The I<source> line is an array of source files required to build the " -"package. Source files must reside in the same directory as the PKGBUILD " -"file, unless they have a fully-qualified URL. Then if the source file does " -"not already exist in /var/cache/pacman/src, the file is downloaded by wget." -msgstr "" - -# type: TP -#: makepkg.8:294 PKGBUILD.8:235 -#, no-wrap -msgid "B<md5sums >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:302 -msgid "" -"If this field is present, it should contain an MD5 hash for every source " -"file specified in the I<source> array (in the same order). makepkg will use " -"this to verify source file integrity during subsequent builds. To easily " -"generate md5sums, first build using the PKGBUILD then run B<makepkg -g " -"E<gt>E<gt>PKGBUILD>. Then you can edit the PKGBUILD and move the I<md5sums> " -"line from the bottom to an appropriate location." -msgstr "" - -# type: TP -#: makepkg.8:303 PKGBUILD.8:261 -#, no-wrap -msgid "B<groups >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:308 PKGBUILD.8:266 -msgid "" -"This is an array of symbolic names that represent groups of packages, " -"allowing you to install multiple packages by requesting a single target. " -"For example, one could install all KDE packages by installing the 'kde' " -"group." -msgstr "" - -# type: TP -#: makepkg.8:309 PKGBUILD.8:273 -#, no-wrap -msgid "B<backup >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:316 PKGBUILD.8:280 -msgid "" -"A space-delimited array of filenames (without a preceding slash). The " -"I<backup> line will be propagated to the package meta-info file for pacman. " -"This will designate all files listed there to be backed up if this package " -"is ever removed from a system. See B<HANDLING CONFIG FILES> in the " -"I<pacman> manpage for more information." -msgstr "" - -# type: TP -#: makepkg.8:317 PKGBUILD.8:281 -#, no-wrap -msgid "B<depends >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:325 PKGBUILD.8:289 -msgid "" -"An array of packages that this package depends on to build and run. " -"Packages in this list should be surrounded with single quotes and contain at " -"least the package name. They can also include a version requirement of the " -"form B<nameE<lt>E<gt>version>, where E<lt>E<gt> is one of these three " -"comparisons: B<E<gt>=> (greater than equal to), B<E<lt>=> (less than or " -"equal to), or B<=> (equal to). See the PKGBUILD example above for an " -"example of the I<depends> directive." -msgstr "" - -# type: TP -#: makepkg.8:326 PKGBUILD.8:290 -#, no-wrap -msgid "B<makedepends >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:330 PKGBUILD.8:294 -msgid "" -"An array of packages that this package depends on to build (ie, not required " -"to run). Packages in this list should follow the same format as I<depends>." -msgstr "" - -# type: TP -#: makepkg.8:331 PKGBUILD.8:303 -#, no-wrap -msgid "B<conflicts >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:336 PKGBUILD.8:308 -msgid "" -"An array of packages that will conflict with this package (ie, they cannot " -"both be installed at the same time). This directive follows the same format " -"as I<depends> except you cannot specify versions here, only package names." -msgstr "" - -# type: TP -#: makepkg.8:337 PKGBUILD.8:309 -#, no-wrap -msgid "B<provides >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:343 PKGBUILD.8:315 -msgid "" -"An array of \"virtual provisions\" that this package provides. This allows " -"a package to provide dependency names other than it's own package name. For " -"example, the kernel-scsi and kernel-ide packages can each provide 'kernel' " -"which allows packages to simply depend on 'kernel' rather than \"kernel-scsi " -"OR kernel-ide OR ...\"" -msgstr "" - -# type: TP -#: makepkg.8:344 PKGBUILD.8:316 -#, no-wrap -msgid "B<replaces >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:350 PKGBUILD.8:322 -msgid "" -"This is an array of packages that this package should replace, and can be " -"used to handle renamed/combined packages. For example, if the kernel " -"package gets renamed to kernel-ide, then subsequent 'pacman -Syu' calls will " -"not pick up the upgrade, due to the differing package names. I<replaces> " -"handles this." -msgstr "" - -# type: SH -#: makepkg.8:351 -#, fuzzy, no-wrap -msgid "MAKEPKG OPTIONS" -msgstr "ELTÁVOLÍTÁSI OPCIÓK" - -# type: TP -#: makepkg.8:352 -#, no-wrap -msgid "B<-b, --builddeps>" -msgstr "" - -# type: Plain text -#: makepkg.8:359 -msgid "" -"Build missing dependencies from source. When makepkg finds missing build-" -"time or run-time dependencies, it will look for the dependencies' PKGBUILD " -"files under $ABSROOT (set in your /etc/makepkg.conf). If it finds them it " -"will run another copy of makepkg to build and install the missing " -"dependencies. The child makepkg calls will be made with the B<-b> and B<-i> " -"options." -msgstr "" - -# type: TP -#: makepkg.8:359 -#, no-wrap -msgid "B<-B, --noccache>" -msgstr "" - -# type: Plain text -#: makepkg.8:362 -msgid "Do not use ccache during build." -msgstr "" - -# type: Plain text -#: makepkg.8:365 -msgid "Clean up leftover work files/directories after a successful build." -msgstr "" - -# type: TP -#: makepkg.8:365 -#, no-wrap -msgid "B<-C, --cleancache>" -msgstr "" - -# type: Plain text -#: makepkg.8:368 -msgid "Removes all source files from the cache directory to free up diskspace." -msgstr "" - -# type: Plain text -#: makepkg.8:373 -msgid "" -"Do not perform any dependency checks. This will let you override/ignore any " -"dependencies required. There's a good chance this option will break the " -"build process if all of the dependencies aren't installed." -msgstr "" - -# type: TP -#: makepkg.8:373 -#, no-wrap -msgid "B<-e, --noextract>" -msgstr "" - -# type: Plain text -#: makepkg.8:378 -msgid "" -"Do not extract source files. Instead, use whatever already exists in the " -"src/ directory. This is handy if you want to go into src and manually patch/" -"tweak code, then make a package out of the result." -msgstr "" - -# type: Plain text -#: makepkg.8:383 -msgid "" -"B<makepkg> will not build a package if a I<pkgname-pkgver-pkgrel.pkg.tar.gz> " -"file already exists in the build directory. You can override this behaviour " -"with the B<--force> switch." -msgstr "" - -# type: TP -#: makepkg.8:383 -#, fuzzy, no-wrap -msgid "B<-g, --genmd5>" -msgstr "B<-A, --add>" - -# type: Plain text -#: makepkg.8:388 -msgid "" -"Download all source files (if required) and use I<md5sum> to generate md5 " -"hashes for each of them. You can then redirect the output into your " -"PKGBUILD for source validation (makepkg -g E<gt>E<gt>PKGBUILD)." -msgstr "" - -# type: Plain text -#: makepkg.8:391 -msgid "Output syntax and commandline options." -msgstr "" - -# type: TP -#: makepkg.8:391 -#, no-wrap -msgid "B<-i, --install>" -msgstr "" - -# type: Plain text -#: makepkg.8:394 -msgid "Install/Upgrade the package after a successful build." -msgstr "" - -# type: TP -#: makepkg.8:394 -#, no-wrap -msgid "B<-j E<lt>jobsE<gt>>" -msgstr "" - -# type: Plain text -#: makepkg.8:398 -msgid "" -"Sets MAKEFLAGS=\"-jE<lt>jobsE<gt>\" before building the package. This is " -"useful for overriding the MAKEFLAGS setting in /etc/makepkg.conf." -msgstr "" - -# type: TP -#: makepkg.8:398 -#, no-wrap -msgid "B<-m, --nocolor>" -msgstr "" - -# type: Plain text -#: makepkg.8:401 -msgid "Disable color in output messages" -msgstr "" - -# type: TP -#: makepkg.8:401 -#, no-wrap -msgid "B<-n, --nostrip>" -msgstr "" - -# type: Plain text -#: makepkg.8:404 -msgid "Do not strip binaries and libraries." -msgstr "" - -# type: TP -#: makepkg.8:404 -#, no-wrap -msgid "B<-o, --nobuild>" -msgstr "" - -# type: Plain text -#: makepkg.8:407 -msgid "Download and extract files only, do not build." -msgstr "" - -# type: TP -#: makepkg.8:407 -#, no-wrap -msgid "B<-p E<lt>buildscriptE<gt>>" -msgstr "" - -# type: Plain text -#: makepkg.8:410 -msgid "" -"Read the package script I<E<lt>buildscriptE<gt>> instead of the default " -"(I<PKGBUILD>)." -msgstr "" - -# type: TP -#: makepkg.8:410 -#, no-wrap -msgid "B<-r, --rmdeps>" -msgstr "" - -# type: Plain text -#: makepkg.8:414 -msgid "" -"Upon successful build, remove any dependencies installed by makepkg/pacman " -"during dependency auto-resolution (using B<-b> or B<-s>)." -msgstr "" - -# type: TP -#: makepkg.8:414 -#, no-wrap -msgid "B<-s, --syncdeps>" -msgstr "" - -# type: Plain text -#: makepkg.8:420 -msgid "" -"Install missing dependencies using pacman. When makepkg finds missing build-" -"time or run-time dependencies, it will run pacman to try and resolve them. " -"If successful, pacman will download the missing packages from a package " -"repository and install them for you." -msgstr "" - -# type: TP -#: makepkg.8:420 -#, fuzzy, no-wrap -msgid "B<-S, --sudosync>" -msgstr "B<-S, --sync>" - -# type: Plain text -#: makepkg.8:425 -msgid "" -"Install missing dependencies using pacman and sudo. This is the same as B<-" -"s> except that makepkg will call pacman with sudo. This means you don't have " -"to build as root to use dependency auto-resolution." -msgstr "" - -# type: TP -#: makepkg.8:425 -#, no-wrap -msgid "B<-w E<lt>destdirE<gt>>" -msgstr "" - -# type: Plain text -#: makepkg.8:429 -msgid "" -"Write the resulting package file to the directory I<E<lt>destdirE<gt>> " -"instead of the current working directory." -msgstr "" - -# type: Plain text -#: makepkg.8:434 -msgid "" -"When calling pacman to resolve dependencies or conflicts, makepkg can pass " -"the I<--noconfirm> option to it so it does not wait for any user input " -"before proceeding with operations." -msgstr "" - -# type: Plain text -#: makepkg.8:438 -msgid "" -"When calling pacman, makepkg can pass the I<--noprogressbar> option to it. " -"This is useful if one is directing makepkg's output to a non-terminal (ie, a " -"file)." -msgstr "" - -# type: Plain text -#: makepkg.8:444 -msgid "" -"Configuration options are stored in I</etc/makepkg.conf>. This file is " -"parsed as a bash script, so you can export any special compiler flags you " -"wish to use. This is helpful for building for different architectures, or " -"with different optimizations." -msgstr "" - -# type: Plain text -#: makepkg.8:447 -msgid "" -"B<NOTE:> This does not guarantee that all package Makefiles will use your " -"exported variables. Some of them are flaky..." -msgstr "" - -# type: Plain text -#: makepkg.8:449 -msgid "B<pacman> is the package manager that uses packages built by makepkg." -msgstr "" - -# type: Plain text -#: makepkg.8:452 -msgid "" -"See the Arch Linux Documentation for package-building guidelines if you wish " -"to contribute packages to the Arch Linux project." -msgstr "" - -# type: TH -#: PKGBUILD.8:1 -#, no-wrap -msgid "PKGBUILD" -msgstr "" - -# type: TH -#: PKGBUILD.8:1 -#, no-wrap -msgid "June 13, 2006" -msgstr "2006. június 13." - -# type: TH -#: PKGBUILD.8:1 -#, fuzzy, no-wrap -msgid "Archlinux Developer Manual" -msgstr "Frugalware Fejlesztõi Kézikönyv" - -# type: Plain text -#: PKGBUILD.8:4 -msgid "PKGBUILD - Archlinux package builder descriptor" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:8 -msgid "" -"This manual page is meant to describe general rules about PKGBUILDs. If " -"you're interested in the package builder B<makepkg> itself, then see its " -"manual page, not this one." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:17 -#, no-wrap -msgid "" -"# Last Modified: Sun, 19 Jun 2005 15:24:32 +0000\n" -"# Compiling Time: 0.17 SBU\n" -"# Maintainer: Name E<lt>email(a)addr.essE<gt>\n" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:27 -#, no-wrap -msgid "" -"pkgname=dvdauthor\n" -"pkgver=0.6.11\n" -"pkgrel=3\n" -"pkgdesc=\"Will generate a DVD movie from a valid mpeg2 stream\"\n" -"depends=('imagemagick' 'libdvdread')\n" -"Finclude sourceforge\n" -"groups=('xapps')\n" -"archs=('i686' 'x86_64')\n" -"sha1sums=('a99ea7ef6e50646b77ad47a015127925053d34ea')\n" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:29 -#, no-wrap -msgid "# optimization OK\n" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:34 -msgid "" -"As you can see, the setup is fairly simple. The first line tracks the time " -"of the last update, this is automatically updated after a successful build." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:37 -msgid "" -"The next line defines its build time. Of course, it depends on your " -"hardware, so we use SBUs instead of minutes as a unit." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:41 -msgid "" -"SBU is the Static Binutils Unit, which means the time \"repoman merge " -"binutils\" takes on your machine. By default makepkg will print out how many " -"seconds the build took. After you built binutils, you should update your /" -"etc/makepkg.conf:" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:43 -msgid "SBU=\"257\"" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:47 -msgid "" -"The line above means compiling binutils on your machine took 257 seconds. " -"Starting from this point, makepkg will print out SBUs instead of seconds " -"after successful builds, and this SBU value will be equal on anyone's " -"machine." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:53 -msgid "" -"If you wish to maintain the package, write your name or nick and e-mail " -"address to the third line. If you don't plan to maintain the package just " -"wrote the PKGBUILD, then write Contributor instead of Maintainer, and then " -"someone can take it and will add his/her line later. Other lines like " -"\"Modified by\" are not allowed. Use the darcs patch comments to mention " -"others if you wish." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:61 -msgid "" -"pkgname defines the package name. It should not contain any uppercase " -"letters. The package version defines the upstream version, while the " -"package release tracks the Archlinux-specific changes. pkgrel should be an " -"integer, pkgrels like 5wanda1 are reserved for security updates. There the " -"rule is the following: If the original package's pkgrel was 4, then " -"increment it once when you add a security patch, but then use 5wanda1, " -"5wanda2 and so on. This way the user can easily upgrade to pkgrel=5 which is " -"in -current." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:64 -msgid "" -"pkgdesc is a short one-line description for the package. Usually taken from " -"the project's homepage or manpage. Try to keep the lenght under 80 chars." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:69 -msgid "" -"depends() is a bash array which defines the dependencies of the package. " -"depends() means the other package is required for building and using the " -"current one. If the dependency is runtime-only, then use rodepends(), if " -"buildtime-only then use makedepends()." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:78 -msgid "" -"The next line is a special Finclude commands which allows you to inherit any " -"directive from a PKGBUILD scheme. They can be found in the FST, under /" -"source/include. The \"util\" scheme always included, since its provided " -"functions are used by almost every PKGBUILD. Look at the /source/include/" -"sourceforge.sh, it provides the url, up2date and source() directives, so we " -"don't have to specify them here. After the Finclude you can overwrite the " -"inherited directives, for example define a custom up2date if the inherited " -"one is not sutable for you." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:82 -msgid "" -"The groups() array's first element can't be omitted, and it should be a " -"valid \"first group\". This means it should be in a foo or foo-extra format, " -"where foo or foo-extra is a dir under /source in the FST." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:90 -msgid "" -"The archs() array defines for which architectures the given package is " -"available. If it's not available, it means that gensync will skip it when " -"generating package databases. If you are not able to provide a binary " -"package for a given arch, don't include that in archs()! For example, no " -"matter if the package could be compiled in x86_64, if you haven't compiled " -"it yourself, don't include it. If you're sure it won't be available on a " -"given arch (for example it's written in x86 asm), then use !arch, for " -"example !x86_64." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:95 -msgid "" -"The sha1sums() array can be generated with the makepkg -g command. Its " -"purpose is to prevent compiling from wrong sources, especially when the " -"build is automatic. Where it is available you can use signatures(), its goal " -"is that you don't have to update it manually every time." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:103 -msgid "" -"The last line will be added automatically to the end of the PKGBUILD if the " -"build() function used your $CFLAGS or $CXXFLAGS. This is handy if you want " -"to cross-compile on a faster machine for a slower architecture. Until the " -"package doesn't use our $CFLAGS we can't cross-compile it, so please try to " -"avoid creating \"unoptimized\" packages. If the package doesn't contain any " -"architecture-dependent file, then you can add this line manually as makepkg " -"will not detect this." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:111 -msgid "" -"Finally we define a build() function that will build the package. If you " -"don't want to do anything special, probably you don't have to specify " -"anything, as the default build() (inherited from util.sh) will fit your " -"needs. Even if you define a custom build(), probably you can re-use parts of " -"the default build(). For the list of special functions provided by util.sh " -"and others refer to the /source/include dir. Again, util.sh is included " -"automatically, but you have to Finclude the others before using them!" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:117 -msgid "" -"Once the package is successfully installed into the package root, I<makepkg> " -"will prepare some documentation. It will then strip debugging info from " -"libraries and binaries and generate a meta-info file. Finally, it will " -"compress everything into a .fpm file and leave it in the directory you ran " -"B<makepkg> from." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:120 -msgid "" -"At this point you should have a package file in the current directory, named " -"something like name-version-release-arch.fpm. Done!" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:163 -msgid "" -"The install script does not need to be specified in the I<source> array. If " -"you omit the install directive then makepkg will check for the $pkgname." -"install install and will use it if it's present." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:166 -msgid "" -"You can find a scriptlet skeleton in the /docs/tech/skel/ directory, use it " -"when creating new packages." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:168 -msgid "" -"The scriptlet messages are parsed, a simple example tells you everything:" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:177 -#, no-wrap -msgid "" -"post_upgrade()\n" -"{\n" -"\techo \"START this will be good\"\n" -"\techo \"DONE 0\"\n" -"\techo \"START this will fail\"\n" -"\techo \"DONE 1\"\n" -"\techo \"old message\"\n" -"}\n" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:192 -msgid "This is the release number specific to Archlinux Linux packages." -msgstr "" - -# type: TP -#: PKGBUILD.8:197 -#, no-wrap -msgid "B<pkgdesc_localized>" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:200 -msgid "Array of the localized package descriptions." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:203 -msgid "" -"The format is the following: pkgdesc_localized=('xx_YY foo' 'xx_YY bar')" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:213 -msgid "" -"Sets the license type (eg, \"GPL\", \"BSD\", \"NON-FREE\"). (B<Note>: This " -"option is still in development and may change in the future)" -msgstr "" - -# type: TP -#: PKGBUILD.8:221 -#, no-wrap -msgid "B<up2date>" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:226 -msgid "" -"This directive should contain a command that prints the current upstream " -"stable version of the project. This way we can check for newer version " -"without visiting manually the project's website (see above)." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:243 -msgid "" -"If this field is present, it should contain an MD5 hash for every source " -"file specified in the I<source> array (in the same order). makepkg will use " -"this to verify source file integrity during subsequent builds. To easily " -"generate md5sums, first build using the PKGBUILD then run B<makepkg -G " -"E<gt>E<gt>PKGBUILD>. Then you can edit the PKGBUILD and move the I<md5sums> " -"line from the bottom to an appropriate location." -msgstr "" - -# type: TP -#: PKGBUILD.8:244 -#, no-wrap -msgid "B<sha1sums >I<(array)>" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:252 -msgid "" -"If this field is present, it should contain an SHA1 hash for every source " -"file specified in the I<source> array (in the same order). makepkg will use " -"this to verify source file integrity during subsequent builds. To easily " -"generate sha1sums, first build using the PKGBUILD then run B<makepkg -g " -"E<gt>E<gt>PKGBUILD>. Then you can edit the PKGBUILD and move the " -"I<sha1sums> line from the bottom to an appropriate location." -msgstr "" - -# type: TP -#: PKGBUILD.8:253 -#, no-wrap -msgid "B<signatures >I<(array)>" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:258 -msgid "" -"If this field is present, it should contain an array of gpg signatures " -"required to validate the source files. Where there is no signature available " -"just leave it empty, like:" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:260 -msgid "signatures=(${source[0]}.asc '')" -msgstr "" - -# type: TP -#: PKGBUILD.8:267 -#, no-wrap -msgid "B<archs >I<(array)>" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:272 -msgid "" -"This array defines on which architectures the given package is avalibable. " -"If it's not available, that will mean that gensync will skip it when " -"generating package databases." -msgstr "" - -# type: TP -#: PKGBUILD.8:295 -#, no-wrap -msgid "B<rodepends >I<(array)>" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:302 -msgid "" -"An array of packages that this package depends on to run (ie, not required " -"to build). Generally I<rodepends> should be avoided in favour of I<depends> " -"except where this will create circular dependency chains. (For example " -"building logrotate doesn't requires to have dcron installed.) Packages in " -"this list should follow the same format as I<depends>." -msgstr "" - -# type: TP -#: PKGBUILD.8:323 -#, no-wrap -msgid "B<options >I<(array)>" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:326 -msgid "This is an array of various boolean options. The possible values are:" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:339 -#, no-wrap -msgid "" -"nodocs Don't add any documentation automatically (ie. when there'll be\n" -" a separate documentation subpackage).\n" -"nostrip Don't strip binaries/libraries.\n" -"force This is used to force the package to be upgraded by --sysupgrade,\n" -" even if its an older version.\n" -"nobuild If this directive set, gensync will ignore this package, so users\n" -" must build these packages on their machines, they will not be able\n" -" to install them with pacman -S. Useful for closed-source, but\n" -" freeware programs.\n" -"nofakeroot Don't drop privileges after chrooting. Required by some broken\n" -" packages.\n" -"scriptlet Don't skip executing scriptlets even if we're in chroot.\n" -msgstr "" - -# type: SH -#: PKGBUILD.8:341 -#, no-wrap -msgid "What is the process of chrooted build ?" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:347 -msgid "" -"First, what is chroot? We currently use fakeroot to prevent build() from " -"modifying the host system, and we use a prefix or DESTDIR directive to " -"install everything to a directory and not under to the host system. This is " -"good, but not enough." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:355 -msgid "" -"This system lacks of the ability to control the list of installed packages " -"during the build on the system of a packager, the given compiled package " -"maybe linked itself to an extra installed library. This way we can't really " -"control the list of real dependencies. For example if libquicktime is " -"installed from source on my system, then mplayer or any other program can " -"link itself to that, and so that depends() will be incorrect. Or if I have " -"the closed source binary NVidia drivers installed, some programs link tho " -"NVidia's libraries." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:358 -msgid "" -"Of course there is a sollution to avoid this, to use a real chroot instead " -"of a simple fakeroot. What is this means? The followings:" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:366 -msgid "" -"When starting the build, a core chroot system is installed under /var/" -"chroot. (Of course you can change this value under /etc/makepkg.conf.) The " -"core system contains ~60 packages which are must installed to build any " -"package in a chrooted environment. These packages (for example gcc, kernel-" -"headers, make) should not be mentioned in makedepends(). 'pacman -Sg core " -"chroot-core devel-core' should show you the actial list. (We try to change " -"this list rarely of course.)" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:372 -msgid "" -"When you start building with makepkg -R, pacman will install these packages " -"to /var/chroot if necessary. This will produce a fully \"clean\" Archlinux " -"system, that consits of base packages only. This /var/chroot is fully " -"separated from the host system so that this will solve the problems " -"mentioned above. (Linking to a library installed from source, etc.)" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:377 -msgid "" -"Here comes the fun part. The packages listed in depends() and makedepends() " -"are installed to this clean (/var/chroot) system. From this point, this " -"chroot is capable to build the specified package in it without any " -"unnecessary package installed, fully separated from the host system." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:381 -msgid "" -"After this the chroot should be cleaned up which means the removal of the " -"installed depends() and makedepends(). This ensures us not to build from " -"scratch the core chroot." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:385 -msgid "" -"This way we can prevent lots of dependency problems and it is even possible " -"to build packages for a different Archlinux version. This is quite efficent " -"when building security updates or fixing critical bugs in the -stable tree." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:389 -msgid "" -"If the build is failed, the working directory will not be deleted, you can " -"find it under /var/chroot/var/tmp/fst. Later if you want to clean your " -"chroot (delete the working directory and remove unnecessary packages) you " -"can use 'makepkg -CR'." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:392 -msgid "" -"To activate building in a chroot, you should run makepkg as root at least " -"with the -R option." -msgstr "" - -# type: SH -#: PKGBUILD.8:393 -#, no-wrap -msgid "Package splitting" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:397 -msgid "" -"Package splitting means moving out a list of specifed files to subpackages " -"(like libmysql out of mysql) and then defining the properties of subpackages." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:402 -msgid "" -"NOTE: if you create several subpackages, maintaining those packages will " -"require more and more time. Thus, unnecessary splits aren't welcome. " -"Especially, if you split out a library, then don't move the headers to the " -"package just to speed up building with a few seconds!" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:405 -msgid "" -"The B<subpkgs()> array is to define the pkgnames of the subpackages. From " -"now all the directives has their subfoo equivalent:" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:421 -#, no-wrap -msgid "" -"pkgname -E<gt> subpkgs()\n" -"pkgdesc -E<gt> subdescs()\n" -"pkgdesc_localized -E<gt> subdescs_localized()\n" -"license() -E<gt> sublicense()\n" -"replaces() -E<gt> subreplaces()\n" -"groups() -E<gt> subgroups()\n" -"depends() -E<gt> subdepends()\n" -"rodepends() -E<gt> subrodepends()\n" -"removes() -E<gt> subremoves()\n" -"conflicts() -E<gt> subconflicts()\n" -"provides() -E<gt> subprovides()\n" -"backup() -E<gt> subbackup()\n" -"install -E<gt> subinstall()\n" -"options -E<gt> suboptions()\n" -"archs -E<gt> subarchs()\n" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:425 -msgid "" -"Also note that bash does not support two-dimensional arrays, so when " -"defining the array of arrays, then quotes are the major separators and " -"spaces are the minor ones." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:427 -msgid "Simple example:" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:434 -#, no-wrap -msgid "" -"Add the followings to your bottom of your PKGBUILD\n" -"subpkgs=('foo' 'bar')\n" -"subdescs=('desc of foo' 'desc of bar')\n" -"subdepends=('foodep1 foodep2' 'bardep1 bardep2')\n" -"subgroups=('apps' 'apps')\n" -"subarchs=('i686 x86_64' 'i686 x86_64')\n" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:438 -msgid "" -"You may define conflicts, replaces and other directives for your " -"subpackages, but the requirement is only to define these 5 ones." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:443 -msgid "" -"The second part is to move some files to the - just defined - subpackages. " -"You should use the Fsplit command for this at the end of your build() " -"function. You can read more about Fsplit in the fwmakepkg documentation, but " -"here is a short example:" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:446 -#, no-wrap -msgid "Fsplit subpkgname usr/share/\n" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:449 -msgid "" -"This will move the /usr/share dir of the package to the \"subpkgname\" " -"subpackage." -msgstr "" - -# type: Plain text -#: PKGBUILD.8:452 -msgid "" -"NOTE: never use a trailing slash when defining file patterns, especially if " -"you use wildcards in it!" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:456 -msgid "B<makepkg>(8), B<pacman>(8)" -msgstr "" - -# type: Plain text -#: PKGBUILD.8:460 -#, no-wrap -msgid "" -"Judd Vinet E<lt>jvinet(a)zeroflux.orgE<gt>\n" -"and the Frugalware developers E<lt>frugalware-devel(a)frugalware.orgE<gt>\n" -msgstr "" - -# type: SH -#, fuzzy -#~ msgid "FrugalBuild" -#~ msgstr "FrugalBuild példa:" - -# type: SH -#~ msgid "FrugalBuild Example:" -#~ msgstr "FrugalBuild példa:" - -# type: TH -#~ msgid "Frugalware User Manual" -#~ msgstr "Frugalware Felhasználói Kézikönyv" - -# type: TP -#~ msgid "B<-c, --changelog>" -#~ msgstr "B<-c, --changelog>" - -# type: TP -#~ msgid "B<--ask E<lt>numberE<gt>>" -#~ msgstr "B<--ask E<lt>számE<gt>>" - -# type: TP -#~ msgid "B<-e, --dependsonly>" -#~ msgstr "B<-e, --dependsonly>" Index: pacman-lib/doc/po/pacman.pot diff -u pacman-lib/doc/po/pacman.pot:1.6 pacman-lib/doc/po/pacman.pot:removed --- pacman-lib/doc/po/pacman.pot:1.6 Tue Jan 30 02:47:19 2007 +++ pacman-lib/doc/po/pacman.pot Wed Feb 7 17:29:23 2007 @@ -1,2563 +0,0 @@ -# SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-01-30 13:43-0600\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL(a)li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=CHARSET\n" -"Content-Transfer-Encoding: ENCODING" - -# type: TH -#: pacman.8:1 -#, no-wrap -msgid "pacman" -msgstr "" - -# type: TH -#: pacman.8:1 -#, no-wrap -msgid "January 21, 2006" -msgstr "" - -# type: TH -#: pacman.8:1 -#, no-wrap -msgid "pacman 3.0.0" -msgstr "" - -# type: SH -#: pacman.8:2 makepkg.8:2 ./PKGBUILD.8:2 -#, no-wrap -msgid "NAME" -msgstr "" - -# type: Plain text -#: pacman.8:4 -msgid "pacman - package manager utility" -msgstr "" - -# type: SH -#: pacman.8:4 makepkg.8:4 -#, no-wrap -msgid "SYNOPSIS" -msgstr "" - -# type: Plain text -#: pacman.8:6 -msgid "B<pacman E<lt>operationE<gt> [options] E<lt>packageE<gt> [package] ...>" -msgstr "" - -# type: SH -#: pacman.8:6 makepkg.8:6 ./PKGBUILD.8:4 -#, no-wrap -msgid "DESCRIPTION" -msgstr "" - -# type: Plain text -#: pacman.8:11 -msgid "" -"B<pacman> is a I<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 package are I<gzipped tar> format." -msgstr "" - -# type: SH -#: pacman.8:11 -#, no-wrap -msgid "OPERATIONS" -msgstr "" - -# type: TP -#: pacman.8:12 -#, no-wrap -msgid "B<-A, --add>" -msgstr "" - -# type: Plain text -#: pacman.8:16 -msgid "" -"Add a package to the system. Package will be uncompressed into the " -"installation root and the database will be updated." -msgstr "" - -# type: TP -#: pacman.8:16 -#, no-wrap -msgid "B<-F, --freshen>" -msgstr "" - -# type: Plain text -#: pacman.8:20 -msgid "" -"This is like --upgrade except that, unlike --upgrade, this will only upgrade " -"packages that are already installed on your system." -msgstr "" - -# type: TP -#: pacman.8:20 -#, no-wrap -msgid "B<-Q, --query>" -msgstr "" - -# type: Plain text -#: pacman.8:28 -msgid "" -"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 .tar.gz " -"packages. See B<QUERY OPTIONS> below." -msgstr "" - -# type: TP -#: pacman.8:28 -#, no-wrap -msgid "B<-R, --remove>" -msgstr "" - -# type: Plain text -#: pacman.8:35 -msgid "" -"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 I<.pacsave> extension unless the B<--nosave> option was " -"used." -msgstr "" - -# type: TP -#: pacman.8:35 -#, no-wrap -msgid "B<-S, --sync>" -msgstr "" - -# type: Plain text -#: pacman.8:42 -msgid "" -"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, B<pacman -S qt> will download qt and all the " -"packages it depends on and install them. You could also use B<pacman -Su> to " -"upgrade all packages that are out of date (see below)." -msgstr "" - -# type: TP -#: pacman.8:42 -#, no-wrap -msgid "B<-U, --upgrade>" -msgstr "" - -# type: Plain text -#: pacman.8:47 -msgid "" -"Upgrade a package. This is essentially a \"remove-then-add\" process. See " -"B<HANDLING CONFIG FILES> for an explanation on how pacman takes care of " -"config files." -msgstr "" - -# type: TP -#: pacman.8:47 -#, no-wrap -msgid "B<-V, --version>" -msgstr "" - -# type: Plain text -#: pacman.8:50 -msgid "Display version and exit." -msgstr "" - -# type: TP -#: pacman.8:50 makepkg.8:388 -#, no-wrap -msgid "B<-h, --help>" -msgstr "" - -# type: Plain text -#: pacman.8:54 -msgid "" -"Display syntax for the given operation. If no operation was supplied then " -"the general syntax is shown." -msgstr "" - -# type: SH -#: pacman.8:54 -#, no-wrap -msgid "OPTIONS" -msgstr "" - -# type: TP -#: pacman.8:55 makepkg.8:368 -#, no-wrap -msgid "B<-d, --nodeps>" -msgstr "" - -# type: Plain text -#: pacman.8:61 -msgid "" -"Skips all dependency checks. Normally, pacman 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." -msgstr "" - -# type: TP -#: pacman.8:61 makepkg.8:378 -#, no-wrap -msgid "B<-f, --force>" -msgstr "" - -# type: Plain text -#: pacman.8:67 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:67 -#, no-wrap -msgid "B<-r, --root E<lt>pathE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:76 -msgid "" -"Specify alternative installation root (default is \"/\"). This should I<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." -msgstr "" - -# type: TP -#: pacman.8:76 -#, no-wrap -msgid "B<-v, --verbose>" -msgstr "" - -# type: Plain text -#: pacman.8:79 -msgid "Output more status and error messages." -msgstr "" - -# type: TP -#: pacman.8:79 -#, no-wrap -msgid "B<--config E<lt>pathE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:82 -msgid "Specify an alternate configuration file." -msgstr "" - -# type: TP -#: pacman.8:82 makepkg.8:429 -#, no-wrap -msgid "B<--noconfirm>" -msgstr "" - -# type: Plain text -#: pacman.8:86 -msgid "" -"Bypass any and all \"Are you sure?\" messages. It's not a good idea to do " -"this unless you want to run pacman from a script." -msgstr "" - -# type: TP -#: pacman.8:86 makepkg.8:434 -#, no-wrap -msgid "B<--noprogressbar>" -msgstr "" - -# type: Plain text -#: pacman.8:90 -msgid "" -"Do not show a progress bar when downloading files. This can be useful for " -"scripts that call pacman and capture the output." -msgstr "" - -# type: SH -#: pacman.8:90 -#, no-wrap -msgid "SYNC OPTIONS" -msgstr "" - -# type: TP -#: pacman.8:91 makepkg.8:362 -#, no-wrap -msgid "B<-c, --clean>" -msgstr "" - -# type: Plain text -#: pacman.8:98 -msgid "" -"Remove old packages from the cache. When pacman downloads packages, it " -"saves them in I</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 I<old> packages. Use it twice to " -"remove I<all> packages from the cache." -msgstr "" - -# type: TP -#: pacman.8:98 pacman.8:168 -#, no-wrap -msgid "B<-g, --groups>" -msgstr "" - -# type: Plain text -#: pacman.8:102 -msgid "" -"Display all the members for each package group specified. If no group names " -"are provided, all groups will be listed." -msgstr "" - -# type: TP -#: pacman.8:102 pacman.8:172 -#, no-wrap -msgid "B<-i, --info>" -msgstr "" - -# type: Plain text -#: pacman.8:107 -msgid "" -"Display dependency information for a given package. This will search " -"through all repositories for a matching package and display the " -"dependencies, conflicts, etc." -msgstr "" - -# type: TP -#: pacman.8:107 pacman.8:176 -#, no-wrap -msgid "B<-l, --list>" -msgstr "" - -# type: Plain text -#: pacman.8:111 -msgid "" -"List all files in the specified repositories. Multiple repositories can be " -"specified on the command line." -msgstr "" - -# type: TP -#: pacman.8:111 -#, no-wrap -msgid "B<-p, --print-uris>" -msgstr "" - -# type: Plain text -#: pacman.8:116 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:116 pacman.8:192 -#, no-wrap -msgid "B<-s, --search E<lt>regexpE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:120 -msgid "" -"This will search each package in the package list for names or descriptions " -"that matches E<lt>regexpE<gt>." -msgstr "" - -# type: TP -#: pacman.8:120 -#, no-wrap -msgid "B<-u, --sysupgrade>" -msgstr "" - -# type: Plain text -#: pacman.8:128 -msgid "" -"Upgrades all packages that are out of date. pacman will examine every " -"package installed on the system, and if a newer package exists on the server " -"it will upgrade. pacman 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." -msgstr "" - -# type: TP -#: pacman.8:128 -#, no-wrap -msgid "B<-w, --downloadonly>" -msgstr "" - -# type: Plain text -#: pacman.8:131 -msgid "Retrieve all packages from the server, but do not install/upgrade anything." -msgstr "" - -# type: TP -#: pacman.8:131 -#, no-wrap -msgid "B<-y, --refresh>" -msgstr "" - -# type: Plain text -#: pacman.8:136 -msgid "" -"Download a fresh copy of the master package list from the ftp server defined " -"in I</etc/pacman.conf>. This should typically be used each time you use " -"B<--sysupgrade>." -msgstr "" - -# type: TP -#: pacman.8:136 -#, no-wrap -msgid "B<--ignore E<lt>pkgE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:141 -msgid "" -"This option functions exactly the same as the B<IgnorePkg> configuration " -"directive. Sometimes it can be handy to skip some package updates without " -"having to edit I<pacman.conf> each time." -msgstr "" - -# type: SH -#: pacman.8:141 -#, no-wrap -msgid "REMOVE OPTIONS" -msgstr "" - -# type: TP -#: pacman.8:142 -#, no-wrap -msgid "B<-c, --cascade>" -msgstr "" - -# type: Plain text -#: pacman.8:146 -msgid "" -"Remove all target packages, as well as all packages that depend on one or " -"more target packages. This operation is recursive." -msgstr "" - -# type: TP -#: pacman.8:146 -#, no-wrap -msgid "B<-k, --keep>" -msgstr "" - -# type: Plain text -#: pacman.8:149 -msgid "Removes the database entry only. Leaves all files in place." -msgstr "" - -# type: TP -#: pacman.8:149 -#, no-wrap -msgid "B<-n, --nosave>" -msgstr "" - -# type: Plain text -#: pacman.8:156 -msgid "" -"Instructs pacman to ignore file backup designations. Normally, when a file " -"is about to be I<removed> from the system the database is first checked to " -"see if the file should be renamed to a .pacsave extension. If B<--nosave> " -"is used, these designations are ignored and the files are removed." -msgstr "" - -# type: TP -#: pacman.8:156 -#, no-wrap -msgid "B<-s, --recursive>" -msgstr "" - -# type: Plain text -#: pacman.8:162 -msgid "" -"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." -msgstr "" - -# type: SH -#: pacman.8:162 -#, no-wrap -msgid "QUERY OPTIONS" -msgstr "" - -# type: TP -#: pacman.8:163 -#, no-wrap -msgid "B<-e, --orphans>" -msgstr "" - -# type: Plain text -#: pacman.8:168 -msgid "" -"List all packages that were explicitly installed (ie, not pulled in as a " -"dependency by other packages) and are not required by any other packages." -msgstr "" - -# type: Plain text -#: pacman.8:172 -msgid "" -"Display all package members of a named group, or all grouped packages if no " -"name is specified." -msgstr "" - -# type: Plain text -#: pacman.8:176 -msgid "" -"Display information on a given package. If it is used with the B<-p> option " -"then the .PKGINFO file will be printed." -msgstr "" - -# type: Plain text -#: pacman.8:180 -msgid "" -"List all files owned by E<lt>packageE<gt>. Multiple packages can be " -"specified on the command line." -msgstr "" - -# type: TP -#: pacman.8:180 -#, no-wrap -msgid "B<-m, --foreign>" -msgstr "" - -# type: Plain text -#: pacman.8:184 -msgid "" -"List all packages that were not found in the sync database(s). Typically " -"these are packages that were downloaded manually and installed with --add." -msgstr "" - -# type: TP -#: pacman.8:184 -#, no-wrap -msgid "B<-o, --owns E<lt>fileE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:187 -msgid "Search for the package that owns E<lt>fileE<gt>." -msgstr "" - -# type: TP -#: pacman.8:187 -#, no-wrap -msgid "B<-p, --file>" -msgstr "" - -# type: Plain text -#: pacman.8:192 -msgid "" -"Tells pacman 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 B<--info> and B<--list>." -msgstr "" - -# type: Plain text -#: pacman.8:196 -msgid "" -"This will search each locally-installed package for names or descriptions " -"that matches E<lt>regexpE<gt>." -msgstr "" - -# type: SH -#: pacman.8:196 -#, no-wrap -msgid "HANDLING CONFIG FILES" -msgstr "" - -# type: Plain text -#: pacman.8:203 -msgid "" -"pacman 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:" -msgstr "" - -# type: TP -#: pacman.8:203 -#, no-wrap -msgid "original=B<X>, current=B<X>, new=B<X>" -msgstr "" - -# type: Plain text -#: pacman.8:206 -msgid "All three files are the same, so we win either way. Install the new file." -msgstr "" - -# type: TP -#: pacman.8:206 -#, no-wrap -msgid "original=B<X>, current=B<X>, new=B<Y>" -msgstr "" - -# type: Plain text -#: pacman.8:211 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:211 -#, no-wrap -msgid "original=B<X>, current=B<Y>, new=B<X>" -msgstr "" - -# type: Plain text -#: pacman.8:216 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:216 -#, no-wrap -msgid "original=B<X>, current=B<Y>, new=B<Y>" -msgstr "" - -# type: Plain text -#: pacman.8:219 -msgid "" -"The new one is identical to the current one. Win win. Install the new " -"file." -msgstr "" - -# type: TP -#: pacman.8:219 -#, no-wrap -msgid "original=B<X>, current=B<Y>, new=B<Z>" -msgstr "" - -# type: Plain text -#: pacman.8:224 -msgid "" -"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." -msgstr "" - -# type: SH -#: pacman.8:224 makepkg.8:439 -#, no-wrap -msgid "CONFIGURATION" -msgstr "" - -# type: Plain text -#: pacman.8:230 -msgid "" -"pacman will attempt to read I</etc/pacman.conf> each time it is invoked. " -"This configuration file is divided into sections or I<repositories>. Each " -"section defines a package repository that pacman can use when searching for " -"packages in --sync mode. The exception to this is the I<options> section, " -"which defines global options." -msgstr "" - -# type: SH -#: pacman.8:231 -#, no-wrap -msgid "Example:" -msgstr "" - -# type: Plain text -#: pacman.8:237 -#, no-wrap -msgid "" -"[options]\n" -"NoUpgrade = etc/passwd etc/group etc/shadow\n" -"NoUpgrade = etc/fstab\n" -msgstr "" - -# type: Plain text -#: pacman.8:239 -#, no-wrap -msgid "Include = /etc/pacman.d/current\n" -msgstr "" - -# type: Plain text -#: pacman.8:242 -#, no-wrap -msgid "" -"[custom]\n" -"Server = file:///home/pkgs\n" -msgstr "" - -# type: SH -#: pacman.8:245 -#, no-wrap -msgid "CONFIG: OPTIONS" -msgstr "" - -# type: TP -#: pacman.8:246 -#, no-wrap -msgid "B<DBPath = path/to/db/dir>" -msgstr "" - -# type: Plain text -#: pacman.8:253 -msgid "" -"Overrides the default location of the toplevel database directory. The " -"default is I<var/lib/pacman>. B<CacheDir = path/to/cache/dir> Overrides the " -"default location of the package cache directory. The default is " -"I<var/cache/pacman>." -msgstr "" - -# type: TP -#: pacman.8:254 -#, no-wrap -msgid "B<HoldPkg = E<lt>packageE<gt> [package] ...>" -msgstr "" - -# type: Plain text -#: pacman.8:258 -msgid "" -"If a user tries to B<--remove> a package that's listed in HoldPkg, pacman " -"will ask for confirmation before proceeding." -msgstr "" - -# type: TP -#: pacman.8:258 -#, no-wrap -msgid "B<IgnorePkg = E<lt>packageE<gt> [package] ...>" -msgstr "" - -# type: Plain text -#: pacman.8:262 -msgid "" -"Instructs pacman to ignore any upgrades for this package when performing a " -"B<--sysupgrade>." -msgstr "" - -# type: TP -#: pacman.8:262 -#, no-wrap -msgid "B<Include = E<lt>pathE<gt>>" -msgstr "" - -# type: Plain text -#: pacman.8:266 -msgid "" -"Include another config file. This config file can include repositories or " -"general configuration options." -msgstr "" - -# type: TP -#: pacman.8:266 -#, no-wrap -msgid "B<ProxyServer = E<lt>host|ipE<gt>[:port]>" -msgstr "" - -# type: Plain text -#: pacman.8:269 -msgid "If set, pacman will use this proxy server for all ftp/http transfers." -msgstr "" - -# type: TP -#: pacman.8:269 -#, no-wrap -msgid "B<XferCommand = /path/to/command %u>" -msgstr "" - -# type: Plain text -#: pacman.8:275 -msgid "" -"If set, pacman will use this external program to download all remote files. " -"All instances of B<%u> will be replaced with the URL to be downloaded. If " -"present, instances of B<%o> will be replaced with the local filename, plus a " -"\".part\" extension, which allows programs like wget to do file resumes " -"properly." -msgstr "" - -# type: Plain text -#: pacman.8:279 -msgid "" -"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." -msgstr "" - -# type: TP -#: pacman.8:279 -#, no-wrap -msgid "B<NoPassiveFtp>" -msgstr "" - -# type: Plain text -#: pacman.8:282 -msgid "" -"Disables passive ftp connections when downloading packages. (aka Active " -"Mode)" -msgstr "" - -# type: TP -#: pacman.8:282 -#, no-wrap -msgid "B<NoUpgrade = E<lt>fileE<gt> [file] ...>" -msgstr "" - -# type: Plain text -#: pacman.8:286 -msgid "" -"All files listed with a B<NoUpgrade> directive will never be touched during " -"a package install/upgrade. I<Note:> do not include the leading slash when " -"specifying files." -msgstr "" - -# type: TP -#: pacman.8:286 -#, no-wrap -msgid "B<NoExtract = E<lt>fileE<gt> [file] ...>" -msgstr "" - -# type: Plain text -#: pacman.8:293 -msgid "" -"All files listed with a B<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." -msgstr "" - -# type: TP -#: pacman.8:293 -#, no-wrap -msgid "B<UseSyslog>" -msgstr "" - -# type: Plain text -#: pacman.8:297 -msgid "" -"Log action messages through syslog(). This will insert pacman log entries " -"into your /var/log/messages or equivalent." -msgstr "" - -# type: TP -#: pacman.8:297 -#, no-wrap -msgid "B<LogFile = /path/to/file>" -msgstr "" - -# type: Plain text -#: pacman.8:300 -msgid "Log actions directly to a file, usually /var/log/pacman.log." -msgstr "" - -# type: SH -#: pacman.8:301 -#, no-wrap -msgid "CONFIG: REPOSITORIES" -msgstr "" - -# type: Plain text -#: pacman.8:311 -msgid "" -"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 I<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. The order of repositories in the file matters; " -"repositories listed first will take precidence over those listed later in " -"the file when packages in two repositories have identical names, regardless " -"of version number." -msgstr "" - -# type: SH -#: pacman.8:311 -#, no-wrap -msgid "USING YOUR OWN REPOSITORY" -msgstr "" - -# type: Plain text -#: pacman.8:315 -msgid "" -"Let's say you have a bunch of custom packages in I</home/pkgs> and their " -"respective PKGBUILD files are all in I</var/abs/local>. All you need to do " -"is generate a compressed package database in the I</home/pkgs> directory so " -"pacman can find it when run with --refresh." -msgstr "" - -# type: Plain text -#: pacman.8:319 -#, no-wrap -msgid "# gensync /var/abs/local /home/pkgs/custom.db.tar.gz\n" -msgstr "" - -# type: Plain text -#: pacman.8:329 -msgid "" -"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 I<{treename}.db.tar.gz>, where " -"{treename} is the name of the section defined in the configuration file. " -"That's it! Now configure your I<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." -msgstr "" - -# type: SH -#: pacman.8:329 makepkg.8:447 ./PKGBUILD.8:453 -#, no-wrap -msgid "SEE ALSO" -msgstr "" - -# type: Plain text -#: pacman.8:331 -msgid "B<makepkg> is the package-building tool that comes with pacman." -msgstr "" - -# type: SH -#: pacman.8:331 makepkg.8:452 ./PKGBUILD.8:456 -#, no-wrap -msgid "AUTHOR" -msgstr "" - -# type: Plain text -#: pacman.8:334 makepkg.8:455 -#, no-wrap -msgid "Judd Vinet E<lt>jvinet(a)zeroflux.orgE<gt>\n" -msgstr "" - -# type: TH -#: makepkg.8:1 -#, no-wrap -msgid "makepkg" -msgstr "" - -# type: TH -#: makepkg.8:1 -#, no-wrap -msgid "January 30, 2006" -msgstr "" - -# type: TH -#: makepkg.8:1 -#, no-wrap -msgid "makepkg #VERSION#" -msgstr "" - -# type: Plain text -#: makepkg.8:4 -msgid "makepkg - package build utility" -msgstr "" - -# type: Plain text -#: makepkg.8:6 -msgid "B<makepkg [options]>" -msgstr "" - -# type: Plain text -#: makepkg.8:15 -msgid "" -"B<makepkg> will build packages for you. All it needs is a build-capable " -"linux platform, wget, and some build scripts. The advantage to a " -"script-based build is that you only really do the work once. Once you have " -"the build script for a package, you just need to run makepkg and it will do " -"the rest: download and validate source files, check dependencies, configure " -"the buildtime settings, build the package, install the package into a " -"temporary root, make customizations, generate meta-info, and package the " -"whole thing up for B<pacman> to use." -msgstr "" - -# type: Plain text -#: makepkg.8:18 -msgid "" -"B<makeworld> can be used to rebuild an entire package group or the entire " -"build tree. See B<makeworld --help> for syntax." -msgstr "" - -# type: SH -#: makepkg.8:18 -#, no-wrap -msgid "BUILD PROCESS (or How To Build Your Own Packages)" -msgstr "" - -# type: Plain text -#: makepkg.8:22 -msgid "" -"Start in an isolated directory (ie, it's not used for anything other than " -"building this package). The build script should be called PKGBUILD and it " -"should bear resemblance to the example below." -msgstr "" - -# type: Plain text -#: makepkg.8:27 -msgid "" -"B<NOTE:> If you have a local copy of the Arch Build System (ABS) tree on " -"your computer, you can copy the PKGBUILD.proto file to your new package " -"build directory and edit it from there. To acquire/sync the ABS tree, use " -"the B<abs> script included with pacman/makepkg." -msgstr "" - -# type: SH -#: makepkg.8:30 ./PKGBUILD.8:11 -#, no-wrap -msgid "PKGBUILD Example:" -msgstr "" - -# type: Plain text -#: makepkg.8:45 -#, no-wrap -msgid "" -"pkgname=modutils\n" -"pkgver=2.4.25\n" -"pkgrel=1\n" -"pkgdesc=\"Utilities for inserting and removing modules from the linux " -"kernel\"\n" -"url=\"http://www.kernel.org\"\n" -"backup=(etc/modules.conf)\n" -"makedepends=('bash' 'mawk')\n" -"depends=('glibc' 'zlib')\n" -"source=(ftp://ftp.kernel.org/pub/linux/utils/kernel/$pkgname/v2.4/$pkgname-… " -"\\e\n" -" modules.conf)\n" -"md5sums=('2c0cca3ef6330a187c6ef4fe41ecaa4d' \\e\n" -" '35175bee593a7cc7d6205584a94d8625')\n" -msgstr "" - -# type: Plain text -#: makepkg.8:55 -#, no-wrap -msgid "" -"build() {\n" -" cd $startdir/src/$pkgname-$pkgver\n" -" ./configure --prefix=/usr --enable-insmod-static\n" -" make || return 1\n" -" make prefix=$startdir/pkg/usr install\n" -" mv $startdir/pkg/usr/sbin $startdir/pkg\n" -" mkdir -p $startdir/pkg/etc\n" -" cp ../modules.conf $startdir/pkg/etc\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:63 -msgid "" -"As you can see, the setup is fairly simple. The first three lines define " -"the package name and version info. They also define the final package name " -"which will be of the form I<$pkgname-$pkgver-$pkgrel.pkg.tar.gz>. The " -"fourth line provides a brief description of the package. These four lines " -"should be present in every PKGBUILD script." -msgstr "" - -# type: Plain text -#: makepkg.8:67 -msgid "" -"The line with I<backup=> specifies files that should be treated specially " -"when removing or upgrading packages. See B<HANDLING CONFIG FILES> in the " -"I<pacman> manpage for more information on this." -msgstr "" - -# type: Plain text -#: makepkg.8:73 -msgid "" -"Lines 7 and 8 list the dependencies for this package. The I<depends> array " -"specifies the run-time dependencies and I<makedepends> specifies the " -"build-time dependencies. In order to run the package, I<depends> must be " -"satisfied. To build the package, B<all> dependencies must be satisifed " -"first. makepkg will check this before attempting to build the package." -msgstr "" - -# type: Plain text -#: makepkg.8:77 -msgid "" -"The I<source> array tells makepkg which files to download/extract before " -"compiling begins. The I<md5sums> array provides md5sums for each of these " -"files. These are used to validate the integrity of the source files." -msgstr "" - -# type: Plain text -#: makepkg.8:82 -msgid "" -"Once your PKGBUILD is created, you can run I<makepkg> from the build " -"directory. makepkg will then check dependencies and look for the source " -"files required to build. If some are missing it will attempt to download " -"them, provided there is a fully-qualified URL in the I<source> array." -msgstr "" - -# type: Plain text -#: makepkg.8:87 -msgid "" -"The sources are then extracted into a directory called ./src and the " -"I<build> function is called. This is where all package configuration, " -"building, and installing should be done. Any customization will likely take " -"place here." -msgstr "" - -# type: Plain text -#: makepkg.8:91 -msgid "" -"After a package is built, the I<build> function must install the package " -"files into a special package root, which can be referenced by " -"B<$startdir/pkg> in the I<build> function. The typical way to do this is " -"one of the following:" -msgstr "" - -# type: Plain text -#: makepkg.8:95 -#, no-wrap -msgid "make DESTDIR=$startdir/pkg install\n" -msgstr "" - -# type: Plain text -#: makepkg.8:97 -#, no-wrap -msgid "or\n" -msgstr "" - -# type: Plain text -#: makepkg.8:99 -#, no-wrap -msgid "make prefix=$startdir/pkg/usr install\n" -msgstr "" - -# type: Plain text -#: makepkg.8:105 -msgid "" -"Notice that the \"/usr\" portion should be present with \"prefix\", but not " -"\"DESTDIR\". \"DESTDIR\" is the favorable option to use, but not all " -"Makefiles support it. Use \"prefix\" only when \"DESTDIR\" is unavailable." -msgstr "" - -# type: Plain text -#: makepkg.8:112 -msgid "" -"Once the package is successfully installed into the package root, I<makepkg> " -"will remove some directories (as per Arch Linux package guidelines; if you " -"use this elsewhere, feel free to change it) like /usr/doc and /usr/info. It " -"will then strip debugging info from libraries and binaries and generate a " -"meta-info file. Finally, it will compress everything into a .pkg.tar.gz " -"file and leave it in the directory you ran B<makepkg> from." -msgstr "" - -# type: Plain text -#: makepkg.8:115 -msgid "" -"At this point you should have a package file in the current directory, named " -"something like name-version-release.pkg.tar.gz. Done!" -msgstr "" - -# type: SH -#: makepkg.8:116 ./PKGBUILD.8:121 -#, no-wrap -msgid "Install/Upgrade/Remove Scripting" -msgstr "" - -# type: Plain text -#: makepkg.8:120 ./PKGBUILD.8:125 -msgid "" -"Pacman has the ability to store and execute a package-specific script when " -"it installs, removes, or upgrades a package. This allows a package to " -"\"configure itself\" after installation and do the opposite right before it " -"is removed." -msgstr "" - -# type: Plain text -#: makepkg.8:122 ./PKGBUILD.8:127 -msgid "The exact time the script is run varies with each operation:" -msgstr "" - -# type: TP -#: makepkg.8:122 ./PKGBUILD.8:127 -#, no-wrap -msgid "B<pre_install>" -msgstr "" - -# type: Plain text -#: makepkg.8:125 makepkg.8:133 ./PKGBUILD.8:130 ./PKGBUILD.8:138 -msgid "script is run right before files are extracted." -msgstr "" - -# type: TP -#: makepkg.8:126 ./PKGBUILD.8:131 -#, no-wrap -msgid "B<post_install>" -msgstr "" - -# type: Plain text -#: makepkg.8:129 ./PKGBUILD.8:134 -msgid "script is run right after files are extracted." -msgstr "" - -# type: TP -#: makepkg.8:130 ./PKGBUILD.8:135 -#, no-wrap -msgid "B<pre_upgrade>" -msgstr "" - -# type: TP -#: makepkg.8:134 ./PKGBUILD.8:139 -#, no-wrap -msgid "B<post_upgrade>" -msgstr "" - -# type: Plain text -#: makepkg.8:137 ./PKGBUILD.8:142 -msgid "script is run after files are extracted." -msgstr "" - -# type: TP -#: makepkg.8:138 ./PKGBUILD.8:143 -#, no-wrap -msgid "B<pre_remove>" -msgstr "" - -# type: Plain text -#: makepkg.8:141 ./PKGBUILD.8:146 -msgid "script is run right before files are removed." -msgstr "" - -# type: TP -#: makepkg.8:142 ./PKGBUILD.8:147 -#, no-wrap -msgid "B<post_remove>" -msgstr "" - -# type: Plain text -#: makepkg.8:145 ./PKGBUILD.8:150 -msgid "script is run right after files are removed." -msgstr "" - -# type: Plain text -#: makepkg.8:149 ./PKGBUILD.8:154 -msgid "" -"To use this feature, just create a file (eg, pkgname.install) and put it in " -"the same directory as the PKGBUILD script. Then use the I<install> " -"directive:" -msgstr "" - -# type: Plain text -#: makepkg.8:152 ./PKGBUILD.8:157 -#, no-wrap -msgid "install=pkgname.install\n" -msgstr "" - -# type: Plain text -#: makepkg.8:156 -msgid "The install script does not need to be specified in the I<source> array." -msgstr "" - -# type: SH -#: makepkg.8:159 -#, no-wrap -msgid "Install scripts must follow this format:" -msgstr "" - -# type: Plain text -#: makepkg.8:169 -#, no-wrap -msgid "" -"# arg 1: the new package version\n" -"pre_install() {\n" -" #\n" -" # do pre-install stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:177 -#, no-wrap -msgid "" -"# arg 1: the new package version\n" -"post_install() {\n" -" #\n" -" # do post-install stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:186 -#, no-wrap -msgid "" -"# arg 1: the new package version\n" -"# arg 2: the old package version\n" -"pre_upgrade() {\n" -" #\n" -" # do pre-upgrade stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:195 -#, no-wrap -msgid "" -"# arg 1: the new package version\n" -"# arg 2: the old package version\n" -"post_upgrade() {\n" -" #\n" -" # do post-upgrade stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:203 -#, no-wrap -msgid "" -"# arg 1: the old package version\n" -"pre_remove() {\n" -" #\n" -" # do pre-remove stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:211 -#, no-wrap -msgid "" -"# arg 1: the old package version\n" -"post_remove() {\n" -" #\n" -" # do post-remove stuff here\n" -" #\n" -" /bin/true\n" -"}\n" -msgstr "" - -# type: Plain text -#: makepkg.8:215 -#, no-wrap -msgid "" -"op=$1\n" -"shift\n" -"$op $*\n" -msgstr "" - -# type: Plain text -#: makepkg.8:219 -msgid "This template is also available in your ABS tree (/var/abs/install.proto)." -msgstr "" - -# type: SH -#: makepkg.8:220 ./PKGBUILD.8:179 -#, no-wrap -msgid "PKGBUILD Directives" -msgstr "" - -# type: TP -#: makepkg.8:221 ./PKGBUILD.8:180 -#, no-wrap -msgid "B<pkgname>" -msgstr "" - -# type: Plain text -#: makepkg.8:225 ./PKGBUILD.8:184 -msgid "" -"The name of the package. This has be a unix-friendly name as it will be " -"used in the package filename." -msgstr "" - -# type: TP -#: makepkg.8:226 ./PKGBUILD.8:185 -#, no-wrap -msgid "B<pkgver>" -msgstr "" - -# type: Plain text -#: makepkg.8:229 ./PKGBUILD.8:188 -msgid "This is the version of the software as released from the author (eg, 2.7.1)." -msgstr "" - -# type: TP -#: makepkg.8:230 ./PKGBUILD.8:189 -#, no-wrap -msgid "B<pkgrel>" -msgstr "" - -# type: Plain text -#: makepkg.8:233 -msgid "This is the release number specific to Arch Linux packages." -msgstr "" - -# type: TP -#: makepkg.8:234 ./PKGBUILD.8:193 -#, no-wrap -msgid "B<pkgdesc>" -msgstr "" - -# type: Plain text -#: makepkg.8:237 ./PKGBUILD.8:196 -msgid "This should be a brief description of the package and its functionality." -msgstr "" - -# type: TP -#: makepkg.8:238 -#, no-wrap -msgid "B<options>" -msgstr "" - -# type: Plain text -#: makepkg.8:243 -msgid "" -"This array allows you to override some of makepkg's default behaviour when " -"building packages. To set an option, just include the option name in the " -"B<options> array." -msgstr "" - -# type: Plain text -#: makepkg.8:246 -msgid "I<Available Options:>" -msgstr "" - -# type: TP -#: makepkg.8:247 -#, no-wrap -msgid "B<FORCE>" -msgstr "" - -# type: Plain text -#: makepkg.8:251 -msgid "" -"force the package to be upgraded by B<--sysupgrade>, even if its an older " -"version." -msgstr "" - -# type: TP -#: makepkg.8:251 -#, no-wrap -msgid "B<KEEPDOCS>" -msgstr "" - -# type: Plain text -#: makepkg.8:254 -msgid "do not remove /usr/share/doc and /usr/share/info directories." -msgstr "" - -# type: TP -#: makepkg.8:254 -#, no-wrap -msgid "B<NOSTRIP>" -msgstr "" - -# type: Plain text -#: makepkg.8:257 -msgid "do not strip debugging symbols from binaries and libraries." -msgstr "" - -# type: TP -#: makepkg.8:260 ./PKGBUILD.8:204 -#, no-wrap -msgid "B<url>" -msgstr "" - -# type: Plain text -#: makepkg.8:264 ./PKGBUILD.8:208 -msgid "" -"This field contains an optional URL that is associated with the piece of " -"software being packaged. This is typically the project's website." -msgstr "" - -# type: TP -#: makepkg.8:265 ./PKGBUILD.8:209 -#, no-wrap -msgid "B<license>" -msgstr "" - -# type: Plain text -#: makepkg.8:275 -msgid "" -"This field specifies the license(s) that apply to the package. " -"Commonly-used licenses are typically found in " -"I</usr/share/licenses/common>. If you see the package's license there, " -"simply reference it in the license field (eg, B<license=\"GPL\">). If the " -"package provides a license not found in I</usr/share/licenses/common>, then " -"you should include the license in the package itself and set " -"B<license=\"custom\"> or B<license=\"custom:LicenseName\">. The license " -"itself should be placed in a directory called " -"I<$startdir/pkg/usr/share/licenses/$pkgname>." -msgstr "" - -# type: Plain text -#: makepkg.8:278 -msgid "" -"If multiple licenses are applied, use the array form: B<license=('GPL' " -"'FDL')>" -msgstr "" - -# type: TP -#: makepkg.8:279 ./PKGBUILD.8:214 -#, no-wrap -msgid "B<install>" -msgstr "" - -# type: Plain text -#: makepkg.8:285 ./PKGBUILD.8:220 -msgid "" -"Specifies a special install script that is to be included in the package. " -"This file should reside in the same directory as the PKGBUILD, and will be " -"copied into the package by makepkg. It does not need to be included in the " -"I<source> array. (eg, install=modutils.install)" -msgstr "" - -# type: TP -#: makepkg.8:286 ./PKGBUILD.8:227 -#, no-wrap -msgid "B<source >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:293 ./PKGBUILD.8:234 -msgid "" -"The I<source> line is an array of source files required to build the " -"package. Source files must reside in the same directory as the PKGBUILD " -"file, unless they have a fully-qualified URL. Then if the source file does " -"not already exist in /var/cache/pacman/src, the file is downloaded by wget." -msgstr "" - -# type: TP -#: makepkg.8:294 ./PKGBUILD.8:235 -#, no-wrap -msgid "B<md5sums >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:302 -msgid "" -"If this field is present, it should contain an MD5 hash for every source " -"file specified in the I<source> array (in the same order). makepkg will use " -"this to verify source file integrity during subsequent builds. To easily " -"generate md5sums, first build using the PKGBUILD then run B<makepkg -g " -"E<gt>E<gt>PKGBUILD>. Then you can edit the PKGBUILD and move the I<md5sums> " -"line from the bottom to an appropriate location." -msgstr "" - -# type: TP -#: makepkg.8:303 ./PKGBUILD.8:261 -#, no-wrap -msgid "B<groups >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:308 ./PKGBUILD.8:266 -msgid "" -"This is an array of symbolic names that represent groups of packages, " -"allowing you to install multiple packages by requesting a single target. " -"For example, one could install all KDE packages by installing the 'kde' " -"group." -msgstr "" - -# type: TP -#: makepkg.8:309 ./PKGBUILD.8:273 -#, no-wrap -msgid "B<backup >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:316 ./PKGBUILD.8:280 -msgid "" -"A space-delimited array of filenames (without a preceding slash). The " -"I<backup> line will be propagated to the package meta-info file for pacman. " -"This will designate all files listed there to be backed up if this package " -"is ever removed from a system. See B<HANDLING CONFIG FILES> in the " -"I<pacman> manpage for more information." -msgstr "" - -# type: TP -#: makepkg.8:317 ./PKGBUILD.8:281 -#, no-wrap -msgid "B<depends >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:325 ./PKGBUILD.8:289 -msgid "" -"An array of packages that this package depends on to build and run. " -"Packages in this list should be surrounded with single quotes and contain at " -"least the package name. They can also include a version requirement of the " -"form B<nameE<lt>E<gt>version>, where E<lt>E<gt> is one of these three " -"comparisons: B<E<gt>=> (greater than equal to), B<E<lt>=> (less than or " -"equal to), or B<=> (equal to). See the PKGBUILD example above for an " -"example of the I<depends> directive." -msgstr "" - -# type: TP -#: makepkg.8:326 ./PKGBUILD.8:290 -#, no-wrap -msgid "B<makedepends >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:330 ./PKGBUILD.8:294 -msgid "" -"An array of packages that this package depends on to build (ie, not required " -"to run). Packages in this list should follow the same format as I<depends>." -msgstr "" - -# type: TP -#: makepkg.8:331 ./PKGBUILD.8:303 -#, no-wrap -msgid "B<conflicts >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:336 ./PKGBUILD.8:308 -msgid "" -"An array of packages that will conflict with this package (ie, they cannot " -"both be installed at the same time). This directive follows the same format " -"as I<depends> except you cannot specify versions here, only package names." -msgstr "" - -# type: TP -#: makepkg.8:337 ./PKGBUILD.8:309 -#, no-wrap -msgid "B<provides >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:343 ./PKGBUILD.8:315 -msgid "" -"An array of \"virtual provisions\" that this package provides. This allows " -"a package to provide dependency names other than it's own package name. For " -"example, the kernel-scsi and kernel-ide packages can each provide 'kernel' " -"which allows packages to simply depend on 'kernel' rather than \"kernel-scsi " -"OR kernel-ide OR ...\"" -msgstr "" - -# type: TP -#: makepkg.8:344 ./PKGBUILD.8:316 -#, no-wrap -msgid "B<replaces >I<(array)>" -msgstr "" - -# type: Plain text -#: makepkg.8:350 ./PKGBUILD.8:322 -msgid "" -"This is an array of packages that this package should replace, and can be " -"used to handle renamed/combined packages. For example, if the kernel " -"package gets renamed to kernel-ide, then subsequent 'pacman -Syu' calls will " -"not pick up the upgrade, due to the differing package names. I<replaces> " -"handles this." -msgstr "" - -# type: SH -#: makepkg.8:351 -#, no-wrap -msgid "MAKEPKG OPTIONS" -msgstr "" - -# type: TP -#: makepkg.8:352 -#, no-wrap -msgid "B<-b, --builddeps>" -msgstr "" - -# type: Plain text -#: makepkg.8:359 -msgid "" -"Build missing dependencies from source. When makepkg finds missing " -"build-time or run-time dependencies, it will look for the dependencies' " -"PKGBUILD files under $ABSROOT (set in your /etc/makepkg.conf). If it finds " -"them it will run another copy of makepkg to build and install the missing " -"dependencies. The child makepkg calls will be made with the B<-b> and B<-i> " -"options." -msgstr "" - -# type: TP -#: makepkg.8:359 -#, no-wrap -msgid "B<-B, --noccache>" -msgstr "" - -# type: Plain text -#: makepkg.8:362 -msgid "Do not use ccache during build." -msgstr "" - -# type: Plain text -#: makepkg.8:365 -msgid "Clean up leftover work files/directories after a successful build." -msgstr "" - -# type: TP -#: makepkg.8:365 -#, no-wrap -msgid "B<-C, --cleancache>" -msgstr "" - -# type: Plain text -#: makepkg.8:368 -msgid "Removes all source files from the cache directory to free up diskspace." -msgstr "" - -# type: Plain text -#: makepkg.8:373 -msgid "" -"Do not perform any dependency checks. This will let you override/ignore any " -"dependencies required. There's a good chance this option will break the " -"build process if all of the dependencies aren't installed." -msgstr "" - -# type: TP -#: makepkg.8:373 -#, no-wrap -msgid "B<-e, --noextract>" -msgstr "" - -# type: Plain text -#: makepkg.8:378 -msgid "" -"Do not extract source files. Instead, use whatever already exists in the " -"src/ directory. This is handy if you want to go into src and manually " -"patch/tweak code, then make a package out of the result." -msgstr "" - -# type: Plain text -#: makepkg.8:383 -msgid "" -"B<makepkg> will not build a package if a I<pkgname-pkgver-pkgrel.pkg.tar.gz> " -"file already exists in the build directory. You can override this behaviour " -"with the B<--force> switch." -msgstr "" - -# type: TP -#: makepkg.8:383 -#, no-wrap -msgid "B<-g, --genmd5>" -msgstr "" - -# type: Plain text -#: makepkg.8:388 -msgid "" -"Download all source files (if required) and use I<md5sum> to generate md5 " -"hashes for each of them. You can then redirect the output into your " -"PKGBUILD for source validation (makepkg -g E<gt>E<gt>PKGBUILD)." -msgstr "" - -# type: Plain text -#: makepkg.8:391 -msgid "Output syntax and commandline options." -msgstr "" - -# type: TP -#: makepkg.8:391 -#, no-wrap -msgid "B<-i, --install>" -msgstr "" - -# type: Plain text -#: makepkg.8:394 -msgid "Install/Upgrade the package after a successful build." -msgstr "" - -# type: TP -#: makepkg.8:394 -#, no-wrap -msgid "B<-j E<lt>jobsE<gt>>" -msgstr "" - -# type: Plain text -#: makepkg.8:398 -msgid "" -"Sets MAKEFLAGS=\"-jE<lt>jobsE<gt>\" before building the package. This is " -"useful for overriding the MAKEFLAGS setting in /etc/makepkg.conf." -msgstr "" - -# type: TP -#: makepkg.8:398 -#, no-wrap -msgid "B<-m, --nocolor>" -msgstr "" - -# type: Plain text -#: makepkg.8:401 -msgid "Disable color in output messages" -msgstr "" - -# type: TP -#: makepkg.8:401 -#, no-wrap -msgid "B<-n, --nostrip>" -msgstr "" - -# type: Plain text -#: makepkg.8:404 -msgid "Do not strip binaries and libraries." -msgstr "" - -# type: TP -#: makepkg.8:404 -#, no-wrap -msgid "B<-o, --nobuild>" -msgstr "" - -# type: Plain text -#: makepkg.8:407 -msgid "Download and extract files only, do not build." -msgstr "" - -# type: TP -#: makepkg.8:407 -#, no-wrap -msgid "B<-p E<lt>buildscriptE<gt>>" -msgstr "" - -# type: Plain text -#: makepkg.8:410 -msgid "" -"Read the package script I<E<lt>buildscriptE<gt>> instead of the default " -"(I<PKGBUILD>)." -msgstr "" - -# type: TP -#: makepkg.8:410 -#, no-wrap -msgid "B<-r, --rmdeps>" -msgstr "" - -# type: Plain text -#: makepkg.8:414 -msgid "" -"Upon successful build, remove any dependencies installed by makepkg/pacman " -"during dependency auto-resolution (using B<-b> or B<-s>)." -msgstr "" - -# type: TP -#: makepkg.8:414 -#, no-wrap -msgid "B<-s, --syncdeps>" -msgstr "" - -# type: Plain text -#: makepkg.8:420 -msgid "" -"Install missing dependencies using pacman. When makepkg finds missing " -"build-time or run-time dependencies, it will run pacman to try and resolve " -"them. If successful, pacman will download the missing packages from a " -"package repository and install them for you." -msgstr "" - -# type: TP -#: makepkg.8:420 -#, no-wrap -msgid "B<-S, --sudosync>" -msgstr "" - -# type: Plain text -#: makepkg.8:425 -msgid "" -"Install missing dependencies using pacman and sudo. This is the same as " -"B<-s> except that makepkg will call pacman with sudo. This means you don't " -"have to build as root to use dependency auto-resolution." -msgstr "" - -# type: TP -#: makepkg.8:425 -#, no-wrap -msgid "B<-w E<lt>destdirE<gt>>" -msgstr "" - -# type: Plain text -#: makepkg.8:429 -msgid "" -"Write the resulting package file to the directory I<E<lt>destdirE<gt>> " -"instead of the current working directory." -msgstr "" - -# type: Plain text -#: makepkg.8:434 -msgid "" -"When calling pacman to resolve dependencies or conflicts, makepkg can pass " -"the I<--noconfirm> option to it so it does not wait for any user input " -"before proceeding with operations." -msgstr "" - -# type: Plain text -#: makepkg.8:438 -msgid "" -"When calling pacman, makepkg can pass the I<--noprogressbar> option to it. " -"This is useful if one is directing makepkg's output to a non-terminal (ie, a " -"file)." -msgstr "" - -# type: Plain text -#: makepkg.8:444 -msgid "" -"Configuration options are stored in I</etc/makepkg.conf>. This file is " -"parsed as a bash script, so you can export any special compiler flags you " -"wish to use. This is helpful for building for different architectures, or " -"with different optimizations." -msgstr "" - -# type: Plain text -#: makepkg.8:447 -msgid "" -"B<NOTE:> This does not guarantee that all package Makefiles will use your " -"exported variables. Some of them are flaky..." -msgstr "" - -# type: Plain text -#: makepkg.8:449 -msgid "B<pacman> is the package manager that uses packages built by makepkg." -msgstr "" - -# type: Plain text -#: makepkg.8:452 -msgid "" -"See the Arch Linux Documentation for package-building guidelines if you wish " -"to contribute packages to the Arch Linux project." -msgstr "" - -# type: TH -#: ./PKGBUILD.8:1 -#, no-wrap -msgid "PKGBUILD" -msgstr "" - -# type: TH -#: ./PKGBUILD.8:1 -#, no-wrap -msgid "June 13, 2006" -msgstr "" - -# type: TH -#: ./PKGBUILD.8:1 -#, no-wrap -msgid "Archlinux Developer Manual" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:4 -msgid "PKGBUILD - Archlinux package builder descriptor" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:8 -msgid "" -"This manual page is meant to describe general rules about PKGBUILDs. If " -"you're interested in the package builder B<makepkg> itself, then see its " -"manual page, not this one." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:17 -#, no-wrap -msgid "" -"# Last Modified: Sun, 19 Jun 2005 15:24:32 +0000\n" -"# Compiling Time: 0.17 SBU\n" -"# Maintainer: Name E<lt>email(a)addr.essE<gt>\n" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:27 -#, no-wrap -msgid "" -"pkgname=dvdauthor\n" -"pkgver=0.6.11\n" -"pkgrel=3\n" -"pkgdesc=\"Will generate a DVD movie from a valid mpeg2 stream\"\n" -"depends=('imagemagick' 'libdvdread')\n" -"Finclude sourceforge\n" -"groups=('xapps')\n" -"archs=('i686' 'x86_64')\n" -"sha1sums=('a99ea7ef6e50646b77ad47a015127925053d34ea')\n" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:29 -#, no-wrap -msgid "# optimization OK\n" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:34 -msgid "" -"As you can see, the setup is fairly simple. The first line tracks the time " -"of the last update, this is automatically updated after a successful build." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:37 -msgid "" -"The next line defines its build time. Of course, it depends on your " -"hardware, so we use SBUs instead of minutes as a unit." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:41 -msgid "" -"SBU is the Static Binutils Unit, which means the time \"repoman merge " -"binutils\" takes on your machine. By default makepkg will print out how many " -"seconds the build took. After you built binutils, you should update your " -"/etc/makepkg.conf:" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:43 -msgid "SBU=\"257\"" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:47 -msgid "" -"The line above means compiling binutils on your machine took 257 seconds. " -"Starting from this point, makepkg will print out SBUs instead of seconds " -"after successful builds, and this SBU value will be equal on anyone's " -"machine." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:53 -msgid "" -"If you wish to maintain the package, write your name or nick and e-mail " -"address to the third line. If you don't plan to maintain the package just " -"wrote the PKGBUILD, then write Contributor instead of Maintainer, and then " -"someone can take it and will add his/her line later. Other lines like " -"\"Modified by\" are not allowed. Use the darcs patch comments to mention " -"others if you wish." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:61 -msgid "" -"pkgname defines the package name. It should not contain any uppercase " -"letters. The package version defines the upstream version, while the " -"package release tracks the Archlinux-specific changes. pkgrel should be an " -"integer, pkgrels like 5wanda1 are reserved for security updates. There the " -"rule is the following: If the original package's pkgrel was 4, then " -"increment it once when you add a security patch, but then use 5wanda1, " -"5wanda2 and so on. This way the user can easily upgrade to pkgrel=5 which is " -"in -current." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:64 -msgid "" -"pkgdesc is a short one-line description for the package. Usually taken from " -"the project's homepage or manpage. Try to keep the lenght under 80 chars." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:69 -msgid "" -"depends() is a bash array which defines the dependencies of the package. " -"depends() means the other package is required for building and using the " -"current one. If the dependency is runtime-only, then use rodepends(), if " -"buildtime-only then use makedepends()." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:78 -msgid "" -"The next line is a special Finclude commands which allows you to inherit any " -"directive from a PKGBUILD scheme. They can be found in the FST, under " -"/source/include. The \"util\" scheme always included, since its provided " -"functions are used by almost every PKGBUILD. Look at the " -"/source/include/sourceforge.sh, it provides the url, up2date and source() " -"directives, so we don't have to specify them here. After the Finclude you " -"can overwrite the inherited directives, for example define a custom up2date " -"if the inherited one is not sutable for you." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:82 -msgid "" -"The groups() array's first element can't be omitted, and it should be a " -"valid \"first group\". This means it should be in a foo or foo-extra format, " -"where foo or foo-extra is a dir under /source in the FST." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:90 -msgid "" -"The archs() array defines for which architectures the given package is " -"available. If it's not available, it means that gensync will skip it when " -"generating package databases. If you are not able to provide a binary " -"package for a given arch, don't include that in archs()! For example, no " -"matter if the package could be compiled in x86_64, if you haven't compiled " -"it yourself, don't include it. If you're sure it won't be available on a " -"given arch (for example it's written in x86 asm), then use !arch, for " -"example !x86_64." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:95 -msgid "" -"The sha1sums() array can be generated with the makepkg -g command. Its " -"purpose is to prevent compiling from wrong sources, especially when the " -"build is automatic. Where it is available you can use signatures(), its goal " -"is that you don't have to update it manually every time." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:103 -msgid "" -"The last line will be added automatically to the end of the PKGBUILD if the " -"build() function used your $CFLAGS or $CXXFLAGS. This is handy if you want " -"to cross-compile on a faster machine for a slower architecture. Until the " -"package doesn't use our $CFLAGS we can't cross-compile it, so please try to " -"avoid creating \"unoptimized\" packages. If the package doesn't contain any " -"architecture-dependent file, then you can add this line manually as makepkg " -"will not detect this." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:111 -msgid "" -"Finally we define a build() function that will build the package. If you " -"don't want to do anything special, probably you don't have to specify " -"anything, as the default build() (inherited from util.sh) will fit your " -"needs. Even if you define a custom build(), probably you can re-use parts of " -"the default build(). For the list of special functions provided by util.sh " -"and others refer to the /source/include dir. Again, util.sh is included " -"automatically, but you have to Finclude the others before using them!" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:117 -msgid "" -"Once the package is successfully installed into the package root, I<makepkg> " -"will prepare some documentation. It will then strip debugging info from " -"libraries and binaries and generate a meta-info file. Finally, it will " -"compress everything into a .fpm file and leave it in the directory you ran " -"B<makepkg> from." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:120 -msgid "" -"At this point you should have a package file in the current directory, named " -"something like name-version-release-arch.fpm. Done!" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:163 -msgid "" -"The install script does not need to be specified in the I<source> array. If " -"you omit the install directive then makepkg will check for the " -"$pkgname.install install and will use it if it's present." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:166 -msgid "" -"You can find a scriptlet skeleton in the /docs/tech/skel/ directory, use it " -"when creating new packages." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:168 -msgid "The scriptlet messages are parsed, a simple example tells you everything:" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:177 -#, no-wrap -msgid "" -"post_upgrade()\n" -"{\n" -"\techo \"START this will be good\"\n" -"\techo \"DONE 0\"\n" -"\techo \"START this will fail\"\n" -"\techo \"DONE 1\"\n" -"\techo \"old message\"\n" -"}\n" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:192 -msgid "This is the release number specific to Archlinux Linux packages." -msgstr "" - -# type: TP -#: ./PKGBUILD.8:197 -#, no-wrap -msgid "B<pkgdesc_localized>" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:200 -msgid "Array of the localized package descriptions." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:203 -msgid "The format is the following: pkgdesc_localized=('xx_YY foo' 'xx_YY bar')" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:213 -msgid "" -"Sets the license type (eg, \"GPL\", \"BSD\", \"NON-FREE\"). (B<Note>: This " -"option is still in development and may change in the future)" -msgstr "" - -# type: TP -#: ./PKGBUILD.8:221 -#, no-wrap -msgid "B<up2date>" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:226 -msgid "" -"This directive should contain a command that prints the current upstream " -"stable version of the project. This way we can check for newer version " -"without visiting manually the project's website (see above)." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:243 -msgid "" -"If this field is present, it should contain an MD5 hash for every source " -"file specified in the I<source> array (in the same order). makepkg will use " -"this to verify source file integrity during subsequent builds. To easily " -"generate md5sums, first build using the PKGBUILD then run B<makepkg -G " -"E<gt>E<gt>PKGBUILD>. Then you can edit the PKGBUILD and move the I<md5sums> " -"line from the bottom to an appropriate location." -msgstr "" - -# type: TP -#: ./PKGBUILD.8:244 -#, no-wrap -msgid "B<sha1sums >I<(array)>" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:252 -msgid "" -"If this field is present, it should contain an SHA1 hash for every source " -"file specified in the I<source> array (in the same order). makepkg will use " -"this to verify source file integrity during subsequent builds. To easily " -"generate sha1sums, first build using the PKGBUILD then run B<makepkg -g " -"E<gt>E<gt>PKGBUILD>. Then you can edit the PKGBUILD and move the " -"I<sha1sums> line from the bottom to an appropriate location." -msgstr "" - -# type: TP -#: ./PKGBUILD.8:253 -#, no-wrap -msgid "B<signatures >I<(array)>" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:258 -msgid "" -"If this field is present, it should contain an array of gpg signatures " -"required to validate the source files. Where there is no signature available " -"just leave it empty, like:" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:260 -msgid "signatures=(${source[0]}.asc '')" -msgstr "" - -# type: TP -#: ./PKGBUILD.8:267 -#, no-wrap -msgid "B<archs >I<(array)>" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:272 -msgid "" -"This array defines on which architectures the given package is avalibable. " -"If it's not available, that will mean that gensync will skip it when " -"generating package databases." -msgstr "" - -# type: TP -#: ./PKGBUILD.8:295 -#, no-wrap -msgid "B<rodepends >I<(array)>" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:302 -msgid "" -"An array of packages that this package depends on to run (ie, not required " -"to build). Generally I<rodepends> should be avoided in favour of I<depends> " -"except where this will create circular dependency chains. (For example " -"building logrotate doesn't requires to have dcron installed.) Packages in " -"this list should follow the same format as I<depends>." -msgstr "" - -# type: TP -#: ./PKGBUILD.8:323 -#, no-wrap -msgid "B<options >I<(array)>" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:326 -msgid "This is an array of various boolean options. The possible values are:" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:339 -#, no-wrap -msgid "" -"nodocs Don't add any documentation automatically (ie. when there'll be\n" -" a separate documentation subpackage).\n" -"nostrip Don't strip binaries/libraries.\n" -"force This is used to force the package to be upgraded by " -"--sysupgrade,\n" -" even if its an older version.\n" -"nobuild If this directive set, gensync will ignore this package, so " -"users\n" -" must build these packages on their machines, they will not be " -"able\n" -" to install them with pacman -S. Useful for closed-source, but\n" -" freeware programs.\n" -"nofakeroot Don't drop privileges after chrooting. Required by some broken\n" -" packages.\n" -"scriptlet Don't skip executing scriptlets even if we're in chroot.\n" -msgstr "" - -# type: SH -#: ./PKGBUILD.8:341 -#, no-wrap -msgid "What is the process of chrooted build ?" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:347 -msgid "" -"First, what is chroot? We currently use fakeroot to prevent build() from " -"modifying the host system, and we use a prefix or DESTDIR directive to " -"install everything to a directory and not under to the host system. This is " -"good, but not enough." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:355 -msgid "" -"This system lacks of the ability to control the list of installed packages " -"during the build on the system of a packager, the given compiled package " -"maybe linked itself to an extra installed library. This way we can't really " -"control the list of real dependencies. For example if libquicktime is " -"installed from source on my system, then mplayer or any other program can " -"link itself to that, and so that depends() will be incorrect. Or if I have " -"the closed source binary NVidia drivers installed, some programs link tho " -"NVidia's libraries." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:358 -msgid "" -"Of course there is a sollution to avoid this, to use a real chroot instead " -"of a simple fakeroot. What is this means? The followings:" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:366 -msgid "" -"When starting the build, a core chroot system is installed under " -"/var/chroot. (Of course you can change this value under /etc/makepkg.conf.) " -"The core system contains ~60 packages which are must installed to build any " -"package in a chrooted environment. These packages (for example gcc, " -"kernel-headers, make) should not be mentioned in makedepends(). 'pacman -Sg " -"core chroot-core devel-core' should show you the actial list. (We try to " -"change this list rarely of course.)" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:372 -msgid "" -"When you start building with makepkg -R, pacman will install these packages " -"to /var/chroot if necessary. This will produce a fully \"clean\" Archlinux " -"system, that consits of base packages only. This /var/chroot is fully " -"separated from the host system so that this will solve the problems " -"mentioned above. (Linking to a library installed from source, etc.)" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:377 -msgid "" -"Here comes the fun part. The packages listed in depends() and makedepends() " -"are installed to this clean (/var/chroot) system. From this point, this " -"chroot is capable to build the specified package in it without any " -"unnecessary package installed, fully separated from the host system." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:381 -msgid "" -"After this the chroot should be cleaned up which means the removal of the " -"installed depends() and makedepends(). This ensures us not to build from " -"scratch the core chroot." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:385 -msgid "" -"This way we can prevent lots of dependency problems and it is even possible " -"to build packages for a different Archlinux version. This is quite efficent " -"when building security updates or fixing critical bugs in the -stable tree." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:389 -msgid "" -"If the build is failed, the working directory will not be deleted, you can " -"find it under /var/chroot/var/tmp/fst. Later if you want to clean your " -"chroot (delete the working directory and remove unnecessary packages) you " -"can use 'makepkg -CR'." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:392 -msgid "" -"To activate building in a chroot, you should run makepkg as root at least " -"with the -R option." -msgstr "" - -# type: SH -#: ./PKGBUILD.8:393 -#, no-wrap -msgid "Package splitting" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:397 -msgid "" -"Package splitting means moving out a list of specifed files to subpackages " -"(like libmysql out of mysql) and then defining the properties of " -"subpackages." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:402 -msgid "" -"NOTE: if you create several subpackages, maintaining those packages will " -"require more and more time. Thus, unnecessary splits aren't welcome. " -"Especially, if you split out a library, then don't move the headers to the " -"package just to speed up building with a few seconds!" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:405 -msgid "" -"The B<subpkgs()> array is to define the pkgnames of the subpackages. From " -"now all the directives has their subfoo equivalent:" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:421 -#, no-wrap -msgid "" -"pkgname -E<gt> subpkgs()\n" -"pkgdesc -E<gt> subdescs()\n" -"pkgdesc_localized -E<gt> subdescs_localized()\n" -"license() -E<gt> sublicense()\n" -"replaces() -E<gt> subreplaces()\n" -"groups() -E<gt> subgroups()\n" -"depends() -E<gt> subdepends()\n" -"rodepends() -E<gt> subrodepends()\n" -"removes() -E<gt> subremoves()\n" -"conflicts() -E<gt> subconflicts()\n" -"provides() -E<gt> subprovides()\n" -"backup() -E<gt> subbackup()\n" -"install -E<gt> subinstall()\n" -"options -E<gt> suboptions()\n" -"archs -E<gt> subarchs()\n" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:425 -msgid "" -"Also note that bash does not support two-dimensional arrays, so when " -"defining the array of arrays, then quotes are the major separators and " -"spaces are the minor ones." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:427 -msgid "Simple example:" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:434 -#, no-wrap -msgid "" -"Add the followings to your bottom of your PKGBUILD\n" -"subpkgs=('foo' 'bar')\n" -"subdescs=('desc of foo' 'desc of bar')\n" -"subdepends=('foodep1 foodep2' 'bardep1 bardep2')\n" -"subgroups=('apps' 'apps')\n" -"subarchs=('i686 x86_64' 'i686 x86_64')\n" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:438 -msgid "" -"You may define conflicts, replaces and other directives for your " -"subpackages, but the requirement is only to define these 5 ones." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:443 -msgid "" -"The second part is to move some files to the - just defined - " -"subpackages. You should use the Fsplit command for this at the end of your " -"build() function. You can read more about Fsplit in the fwmakepkg " -"documentation, but here is a short example:" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:446 -#, no-wrap -msgid "Fsplit subpkgname usr/share/\n" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:449 -msgid "" -"This will move the /usr/share dir of the package to the \"subpkgname\" " -"subpackage." -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:452 -msgid "" -"NOTE: never use a trailing slash when defining file patterns, especially if " -"you use wildcards in it!" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:456 -msgid "B<makepkg>(8), B<pacman>(8)" -msgstr "" - -# type: Plain text -#: ./PKGBUILD.8:460 -#, no-wrap -msgid "" -"Judd Vinet E<lt>jvinet(a)zeroflux.orgE<gt>\n" -"and the Frugalware developers E<lt>frugalware-devel(a)frugalware.orgE<gt>\n" -msgstr "" Index: pacman-lib/doc/po4a.cfg diff -u pacman-lib/doc/po4a.cfg:1.3 pacman-lib/doc/po4a.cfg:removed --- pacman-lib/doc/po4a.cfg:1.3 Tue Feb 6 15:34:32 2007 +++ pacman-lib/doc/po4a.cfg Wed Feb 7 17:29:23 2007 @@ -1,11 +0,0 @@ -[po4a_langs] hu -[po4a_paths] po/pacman.pot $lang:po/$lang.po -[type: man] pacman.8 \ - $lang:$lang/pacman.8 add_$(srcdir)/$lang:addendum.8.$lang \ - opt:"-o groff_code=verbatim -o translate_joined=CW,CE -o no_wrap=CW:CE" -[type: man] makepkg.8 \ - $lang:$lang/makepkg.8 add_$(srcdir)/$lang:addendum.8.$lang \ - opt:"-o groff_code=verbatim -o translate_joined=CW,CE -o no_wrap=CW:CE" -[type: man] $(srcdir)/PKGBUILD.5 \ - $lang:$lang/PKGBUILD.5 add_$(srcdir)/$lang:addendum.8.$lang \ - opt:"-o groff_code=verbatim -o translate_joined=CW,CE -o no_wrap=CW:CE"

1 0

[pacman-dev] CVS update of pacman-lib (5 files)
by dan＠archlinux.org 07 Feb '07

07 Feb '07

Date: Wednesday, February 7, 2007 @ 17:08:38 Author: dan Path: /home/cvs-pacman/pacman-lib Modified: TODO.dan (1.4 -> 1.5) lib/libalpm/alpm.c (1.112 -> 1.113) lib/libalpm/be_files.c (1.25 -> 1.26) Removed: TODO (1.17) TODO.autoconf (1.3) Spruced up the TODOs a bit, got rid of some of them since a lot of it was duplicate anyway. Also removed the last of the ORE tags and replaced them with TODOs. ------------------------+ TODO | 50 ----------------- TODO.autoconf | 24 -------- TODO.dan | 138 ++++++++++++++++++++++++++++------------------- lib/libalpm/alpm.c | 24 +++----- lib/libalpm/be_files.c | 5 - 5 files changed, 97 insertions(+), 144 deletions(-) Index: pacman-lib/TODO diff -u pacman-lib/TODO:1.17 pacman-lib/TODO:removed --- pacman-lib/TODO:1.17 Wed Nov 15 03:02:43 2006 +++ pacman-lib/TODO Wed Feb 7 17:08:38 2007 @@ -1,50 +0,0 @@ -GLOBAL -====== -- ORE tags - are there any left? -- Automake is a PITA. We should switch to just autoconf and hand written - Makefile.in's - -LIBALPM -======= -- review public interface. There seems to be a lot of complication - for consuming front ends for no reason. I have some ideas for a "new and - improved" public interface, but it would be a drastic change. - -- review errors handling (globalise pm_errno usage, improve error - meanings) - - -PACMAN -====== -- review how things are displayed in the frontend (normal display, - verbose mode, which usage for the library log callback, debug levels, ...) - -- review progress / transaction even subsystem - - -TRANSLATION -=========== - -po files --------- -cs.po - mail sent -es.po - created by Matt, pending -fr.po - mail sent -nl.po - mail sent -pl_PL.po - mail sent -pt_BR.po - mail sent -we need to mail them: -pt_PT.po -ru.po -sv.po -zh_CN.po - -manpages --------- -we need to mail them: -es -hu - we need somebody who'll do the work -pl_PL -pt_BR -zh_CN - Index: pacman-lib/TODO.autoconf diff -u pacman-lib/TODO.autoconf:1.3 pacman-lib/TODO.autoconf:removed --- pacman-lib/TODO.autoconf:1.3 Fri Dec 29 12:04:58 2006 +++ pacman-lib/TODO.autoconf Wed Feb 7 17:08:38 2007 @@ -1,24 +0,0 @@ -TODO for autoconf/automake: - -global -====== - -- review autoclean.sh script. Maybe there is a more simple way to do this FULL clean. - -- Many things :)) If you got idea or request, then implement it. - -libalpm and codechanges -======================= - -- Add much more defines in configure.in via options or not. Like CACHEDIR, PKGEXT, etc. - Those will be available from config.h so not need a big codechange. But it is usefull. - The user can specify at the configure what cachedir or pkgext he/she want. And maybe better - for other distros (like frugalware :) ) which are using other PKGEXT or cachedir than default. - -- Review what needed to be in config.h and what not. Probably many #depends which are now hardcoded - into the sources. - - -Christian Hamar alias krix <krics(a)linuxforum.hu> - -2006. aug. 25., Fri, 01.13.36 CEST Index: pacman-lib/TODO.dan diff -u pacman-lib/TODO.dan:1.4 pacman-lib/TODO.dan:1.5 --- pacman-lib/TODO.dan:1.4 Tue Feb 6 17:36:13 2007 +++ pacman-lib/TODO.dan Wed Feb 7 17:08:37 2007 @@ -1,61 +1,91 @@ TODO.dan -This is my personal TODO list. No guarantees if it is out of date and things - no longer apply. If you want to help out with any of it, send me an email. +======== -* Go through all makepkg bugs in flyspray and see if they are rectified: - http://bugs.archlinux.org/index.php?tasks=&project=1&string=makepkg +This is my personal TODO list. No guarantees if it is out of date and things no +longer apply. If you want to help out with any of it, send me an email. -* Documentation- no one likes to write it, but everyone reads it. Work on the - man pages and make sure they are up to date. -* doc/PKGBUILD.5- continue cleanup work -* PKGBUILD man page should be in section 5 and not section 8 - -* Port the libdownload (libfetch) manpage from BSD style to Linux style, or at - very least change references to BSD. - -* Pacman 3.1 - New cache cleaning functionality in pacman - keep installed - version, choose number to keep, etc. Good python script in the forums that - we should try to emulate, perhaps. -* Pacman 3.1 - downgrade feature - allow users to see cached packages and - downgrade to (previous or any?) available options. - -* Pacman 3.1 - Extreme similarity between some of the sync and add code...we - have to be able to abstract more away from sync actions and add actions to - just 'actions' (example: sync,c, add.c, and deptest.c all contain a switch - on PM_DEP_MOD_*). Merge update, add, and sync code when possible, so we - reduce duplication. - -* Pacman 3.1 - List every function, define, etc. in libalpm. Give one - sentence description of each. If it sounds like two are similar, find a way - to combine or refactor them. If it is unnecessary- delete it. Stop keeping - everything clustered in little add/sync/remove parts, allow transactions to - share code. - -* Pacman 3.1 - Go through options list. Decide if namings are good, all options - are still relevant, etc. Ideas for -Re (#6273), changing meaning of -c (has - two meanings, another FS bug), etc. - -* Pacman 3.1 - Possible rewrite of make system. Options: - -- revise to be more static (Aaron mentioned wmii's system) - -- Cmake? It looks intriguing - -* Pacman 3.1 - Rewrite _alpm_sortbydeps to use Topological Sort. Should work - using a standard topo sort algorithm, once the crazy types can be fixed up - a bit. Include a cycle check - print a big error message if this happens. +Go through all makepkg bugs in Flyspray and see if they are rectified: +http://bugs.archlinux.org/index.php?tasks=&project=1&string=makepkg + +Documentation- no one likes to write it, but everyone reads it. Work on the man +pages and make sure they are up to date. Perhaps move man page format to a more +portable source format to make translation easier to keep up-to-date (something +like txt2tags, docbook?) This will need some research. + +Port the libdownload (libfetch) manpage from BSD style to Linux style, or at +very least change references to BSD. + +Pacman 3.1: +=========== + +Updated cache cleaning functionality in pacman - keep installed version, choose +number to keep, etc. Good python script in the forums that we should try to +emulate, perhaps. + +Downgrade feature - allow users to see cached packages and downgrade to +(previous or any?) available options. + +Extreme similarity between some of the sync and add code...we have to be able +to abstract more away from sync actions and add actions to just 'actions' +(example: sync,c, add.c, and deptest.c all contain a switch on PM_DEP_MOD_*). +Merge update, add, and sync code when possible, so we reduce duplication. + +Review progress /transaction event subsystem. (from TODO) + +Add Doxygen comments to every function in libalpm including private functions. +Ensure functions are doing exactly their purpose and nothing more. Find +functions that perform duplicate behavior and merge them. Combine and refactor +others. Delete unnecessary functions. Stop keeping everything clustered in +little add/sync/remove parts, allow transactions to share code. + +Go through options list. Decide if namings are good, all options are still +relevant, etc. Ideas for -Re (#6273), changing meaning of -c (has two meanings, +another FS bug), etc. Remove the -A flag and possibly -D, -T, and -Y if they +can be done by other actions. Possible switch of -U --> -I (#5571). + +Rewrite _alpm_sortbydeps to use Topological Sort. Should work using a standard +topo sort algorithm, once the crazy types can be fixed up a bit. Include a +cycle check - print a big error message if this happens. -- http://en.wikipedia.org/wiki/Topological_sort -- http://everything2.com/?node_id=556079 +Review display and logging functions. There seems to be an abundance of them. +Make it extensible to use color, review what verbose/debug means. Perhaps +separate logging functionality- Pacman has its normal log, and alpm backend +keeps a very simple log file - listing only adds (including syncs) and removes. +This way a consistency list can be kept of what is currently installed and what +isn't, without all the logging junk from the front end. + +If we stick with autotools, add more defines to configure.in, including +CACHEDIR, PKGEXT, so these can be specified at configure time for ease of use +by other distributions which may want to change the defaults. Also, review what +needs to be in config.h and what does not. There may be excess #depends which +are hard coded into the sources. (from TODO.autoconf) + Quick hits: -* unsigned int vs. unsigned -* 'ldd' & 'ldd -u' - many linkages -* possibly split utilities/extras from pacman package -* makepkg3 produces files with arch appended- gensync can't deal with it -* FS #4185 - move where message is logged, perhaps? -* Remove -A flag (and possibly -D, -T, and -Y?) -* ideas mentioned here - http://bbs.archlinux.org/viewtopic.php?id=29450 - add a .install message about mirrors, maybe comment whole file, encourage - rankmirrors usage -* update copyrights -* update pacman website -* finish pacman coding style page -* make indent.pro file for GNU indent +=========== + +unsigned int vs. unsigned- determine a standard and stick with it + +Possibly split utilities/extras from pacman package + +Rewrite gensync/updatesync, and add a 'repo-remove' script + +FS #4185 - move where message is logged, perhaps? + +ideas mentioned here- http://bbs.archlinux.org/viewtopic.php?id=29450- add a +.install message about mirrors, maybe comment whole file, encourage rankmirrors +usage + +Update copyrights (2007) + +Update pacman website, and add/finish pacman coding style page + +Make .indent.pro file for GNU indent (started, but didn't finish) + +Pacman 3 packaging - perhaps include pacman2.static in case something goes +terribly wrong, which I hope it won't + +autogen.sh / autoclean.sh - these seem messy. Can we clean this up? + + Index: pacman-lib/lib/libalpm/alpm.c diff -u pacman-lib/lib/libalpm/alpm.c:1.112 pacman-lib/lib/libalpm/alpm.c:1.113 --- pacman-lib/lib/libalpm/alpm.c:1.112 Wed Feb 7 01:19:40 2007 +++ pacman-lib/lib/libalpm/alpm.c Wed Feb 7 17:08:37 2007 @@ -820,19 +820,17 @@ vsnprintf(str, LOG_STR_LEN, fmt, args); va_end(args); - /* ORE - We should add a prefix to log strings depending on who called us. - If logaction was called by the frontend: - USER: <the frontend log> - and if called internally: - ALPM: <the library log> - Moreover, the frontend should be able to choose its prefix (USER by default?): - pacman: "PACMAN" - kpacman: "KPACMAN" - ... - It allows to share the log file between several frontends and to actually - know who does what */ - + /* TODO We should add a prefix to log strings depending on who called us. + * If logaction was called by the frontend: + * USER: <the frontend log> + * and if called internally: + * ALPM: <the library log> + * Moreover, the frontend should be able to choose its prefix + * (USER by default?): + * pacman: "PACMAN" + * kpacman: "KPACMAN" + * This would allow us to share the log file between several frontends + * and know who does what */ return(_alpm_logaction(handle->usesyslog, handle->logfd, str)); } /** @} */ Index: pacman-lib/lib/libalpm/be_files.c diff -u pacman-lib/lib/libalpm/be_files.c:1.25 pacman-lib/lib/libalpm/be_files.c:1.26 --- pacman-lib/lib/libalpm/be_files.c:1.25 Wed Jan 31 01:48:06 2007 +++ pacman-lib/lib/libalpm/be_files.c Wed Feb 7 17:08:37 2007 @@ -53,9 +53,8 @@ { ALPM_LOG_FUNC; - /* ORE - we should not simply unpack the archive, but better parse it and - db_write each entry (see sync_load_dbarchive to get archive content) */ + /* TODO we should not simply unpack the archive, but better parse it and + * db_write each entry (see sync_load_dbarchive to get archive content) */ _alpm_log(PM_LOG_DEBUG, _("unpacking database '%s'"), dbfile); if(_alpm_unpack(dbfile, db->path, NULL)) {

1 0

[pacman-dev] Release Schedule for 3.0
by Aaron Griffin 07 Feb '07

07 Feb '07

Pacman 3.0 Release Schedule =========================== 2007-01-31 For those of you used to these sorts of schedules, this may seem a big aggressive, for those of you NOT used to it, it may seem slow. I think this is a decent middle ground. I would not want either testing cycle to go LESS than one week, but they could go longer. We should also setup a bug tracker category (temporarily) for pacman 3.0 testing, to get a concise category for bugs and the like. This was suggested by Dan. The following schedule should give us enough time to iron out any and all issues remaining. It is not set in stone, but gives us something to strive for. * 01-31 to 02-07 (one week): RC Testing. Remaining bug fixes This is our current setup where it seems to be only devs and people on pacman-dev doing testing * 02-07 to 02-14 (one week): Public testing - NOT in repos yet Provide a URL in a news item or forum announcement * 02-14 / 02-15: Release to [testing] repo At this point we will also remove the "side-by-side" scheme (pacman-rc -> pacman) currently used * 02-15 to 02-22 (one week): Public testing This is aggressive and will require us to actually prod people to test / report things * 02-22 / 02-23: Release to [current] * 02-23 - 03-01: Watch and wait for some time. There will be problems at this point and we should address them ASAP. * 03-01 +: Begin pacman 3.1 feature additions and other fun stuff

6 26

← Newer
1
...
19
20
21
22
23
24
25
...
28
Older →

Jump to page: