- Pacman-dev - lists.archlinux.org

[pacman-dev] makepkg: unsetting variables
by Alexander Baldeck 06 Dec '06

06 Dec '06

Hey again, sorry for being such a nagger today. Then again, I have a problem with this change - see attachment - to makepkg. Imagine you want to build glibc from Archlinux ABS. I have two cases for you in which it starts messing things up: 1) comparisons in if-clauses make makepkg freak out The following example: if [ "${CARCH}" = "i686" ]; then # Hack to fix NPTL issues with Xen, only required on 32bit platforms export CFLAGS="${CFLAGS} -mno-tls-direct-seg-refs" fi causes: /usr/bin/makepkg: line 415: unset: `[': not a valid identifier /usr/bin/makepkg: line 415: unset: `"${CARCH}"': not a valid identifier /usr/bin/makepkg: line 415: unset: `=': not a valid identifier /usr/bin/makepkg: line 415: unset: `"i686"': not a valid identifier 2) appending strings in bash-style does not work anymore After getting rid of the if-clauses in the PKGBUILD for the sake of testing, a line like this: $ CFLAGS="-O2" $ export CFLAGS="${CFLAGS} -mno-tls-direct-seg-refs" will result in: $ echo $CFLAGS $ -mno-tls-direct-seg-refs This can't be right... sorry. Since the commit message shows that frugal changes were merged at that time plus that they may still be incomplete, I understand the fact that it might not be ready for general use but at least import something that doesn't fail so obviously. :) BTW, is there no bug tracker for pacman? Cheers, -O

3 3

[pacman-dev] makepkg.conf: problematic assumption for ppc
by Alex 06 Dec '06

06 Dec '06

Hey all, the autotool stuff for pacman-lib writes a makepkg.conf with the following C/XXFLAGS when configured on ppc: CFLAGS="-mcpu=750 -O2 -pipe" CXXFLAGS="-mcpu=750 -O2 -pipe" This is problematic! The past has shown us on archppc that -mcpu=750 might cause problems on G4 AND earlier variants of the PowerPC such as the 604 (pre-G3). Instead we started to use: export CFLAGS="-mtune=powerpc -O2 -pipe -mpowerpc-gfxopt -fPIC" export CXXFLAGS="-mtune=powerpc -O2 -pipe -mpowerpc-gfxopt -fPIC" of which "-mtune=powerpc" is the one which can be generalized, as opposed to "-mpowerpc-gfxopt" which will break compatibility to POWER which is the way I decided to go with archppc. -mtune is a relaxed optimization as you can see. It has proven to produce stable code on all PowerPCs we've seen so far. Also, I'd like to suggest to add "-fPIC" as a ppc default as well. Relocation does not work the way it does on x86 PHP 5.1+ being the most prominent representative for the problem. Every single library it links against must be built with -fPIC in order to load extensions in php.ini. This is only one example. Cheers, -Z

1 0

[pacman-dev] mtab required to install packages; intended behaviour?
by Alex 06 Dec '06

06 Dec '06

Hey all, I just gave the latest Pacman CVS state a go on archppc. I ran into a few problems of which one made me curious about wether this was intended or not. Let me explain: To try pacman fully, I decided to build a archppc/base. First I was trying quickinst with new pacman3 on my root system. It segfaulted, if this issue is not known, let me know. Anyway, installed the chroot with pacman 2.9.8 and rebuilt pacman3 inside of it. When instaling mc it was saying that there was not enough space left. Come to think of it, `df -h` doesn't really say anything cos of missing mtab. Is this intended? Cheers, -I

2 1

[pacman-dev] Fix alignment in package.c of new uncompressed field
by Dan McGee 22 Nov '06

22 Nov '06

Here is a possibility for fixing the 'too big' size of Size (uncompressed). It still makes sense and fits a lot better. Now the dilemma comes if you want to change 'usize' to 'isize'. Dan --- pacman-lib.orig/src/pacman/package.c 2006-11-20 09:59:18.000000000 -0500 +++ pacman-lib/src/pacman/package.c 2006-11-20 21:21:41.000000000 -0500 @@ -147,7 +147,7 @@ pmlist_display(_("Replaces :"), alpm_pkg_get_replaces(pkg)); printf(_("Size (compressed) : %ld\n"), (long)alpm_pkg_get_size(pkg)); - printf(_("Size (uncompressed):%ld\n"), (long)alpm_pkg_get_usize(pkg)); + printf(_("Size (installed) : %ld\n"), (long)alpm_pkg_get_usize(pkg)); printf(_("Description : ")); indentprint(alpm_pkg_get_desc(pkg), 20);

3 2

[pacman-dev] makepkg Patch for consistancy
by Daniel McGee 17 Nov '06

17 Nov '06

Forgot to put this in the last email. That last section in makepkg.conf (FUNCTIONALITY CONFIGURATION) is not something that users of a particular distro will be tweaking- it should pretty much stay the same. Should/could something like this be moved into the makepkg script itself? That way it is still 'variablized', but is more integrated as part of the program itself and less as a configuration option. Dan

3 2

[pacman-dev] [PATCH] typo fix in libdownload
by VMiklos 17 Nov '06

17 Nov '06

hi http://frugalware.org/~vmiklos/patches/libdownload-1.0-typo.diff fix the Makefile's uninstall target udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

1 0

[pacman-dev] libfetch status
by VMiklos 17 Nov '06

17 Nov '06

hi Aaron (and others), what's the status of libfetch at the moment? i mean do you plan to release a separate tarball then it could be a makedepend for pacman? if so, when do you plan to do so? thanks for the info, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 3

[pacman-dev] how stable is libalpm?
by Christ Schlacta 16 Nov '06

16 Nov '06

how stable are the interfaces in libalpm? I'm contemplating writing a GTK based pacman replacement using libalpm, but only if the interfaces in it are stable enough that I won't be constantly playing catchup.

2 1

[pacman-dev] makepkg Patch for consistancy
by Daniel McGee 16 Nov '06

16 Nov '06

This patch implements two consistency issues I think are present in makepkg. Once again, use what you want, not trying to force a patch down your throat. 1. DISTCC was a variable without 'USE_' or 'NO' attached, so I changed it to USE_DISTCC. 2. Undocumented options are present in the makepkg script so I made these options available in makepkg.conf with explanations. The script also needed slightly changing to accommodate these. Dan ________ diff -Naur pacman-lib.orig/etc/makepkg.conf.in pacman-lib/etc/makepkg.conf.in --- pacman-lib.orig/etc/makepkg.conf.in 2006-11-15 15:22:46.000000000 -0500 +++ pacman-lib/etc/makepkg.conf.in 2006-11-15 16:36:58.000000000 -0500 @@ -6,7 +6,7 @@ # SOURCE ACQUISITION ######################################################################### # -#-- The FTP/HTTP download utility that makepkg should use to acquire sources +#-- The FTP/HTTP download utility makepkg should use to acquire sources FTPAGENT="/usr/bin/wget --continue --passive-ftp --tries=3 --waitretry=3 --no-check-certificate" #FTPAGENT="/usr/bin/snarf" #FTPAGENT="/usr/bin/lftpget -c" @@ -18,7 +18,7 @@ CARCH="@CARCH@" CHOST="@CHOST@" -#-- Exclusive: will only run on i686 or higher (P6, Athlon) +#-- Exclusive: will only run on @CARCHFLAGS@ CFLAGS="-@MARCHFLAG@=@CARCHFLAGS@ -O2 -pipe" CXXFLAGS="-@MARCHFLAG@=@CARCHFLAGS@ -O2 -pipe" #-- Optimized: will run on any x86, but optimized for i686 @@ -34,7 +34,7 @@ #-- Fakeroot: for building packages as a non-root user USE_FAKEROOT="y" #-- DistCC: a distributed C/C++/ObjC compiler (modify MAKEFLAGS too) -DISTCC="n" +USE_DISTCC="n" #-- A space-delimited list of hosts running in the DistCC cluster DISTCC_HOSTS="" #-- Colorized output messages @@ -44,10 +44,15 @@ # GLOBAL PACKAGE OPTIONS ######################################################################### # -#-- Don't strip symbols from binaries/libraries -NOSTRIP=0 -#-- Keep doc and info directories +#-- Keep doc and info directories? KEEPDOCS=0 +#-- Don't strip symbols from binaries/libraries? +NOSTRIP=0 +#-- Don't remove libtool files? +#NOLIBTOOL=0 +#-- Don't remove empty directories from package? +#NOEMPTYDIRS=0 ######################################################################### # PACKAGE OUTPUT @@ -59,13 +64,13 @@ #PACKAGER="John Doe <john(a)doe.com>" ######################################################################### -# Functionality Configuration -# Most of this will probably not need to be changed by and end user +# FUNCTIONALITY CONFIGURATION +# (not likely to need changes by the end user) ######################################################################### # BUILDSCRIPT="PKGBUILD" PKGEXT="pkg.tar.gz" -INTEGRITY_CHECK="sha1" +INTEGRITY_CHECK="md5" source "/etc/abs/abs.conf" SRCROOT=$ABSROOT diff -Naur pacman-lib.orig/scripts/makepkg pacman-lib/scripts/makepkg --- pacman-lib.orig/scripts/makepkg 2006-11-15 15:22:46.000000000 -0500 +++ pacman-lib/scripts/makepkg 2006-11-15 16:37:01.000000000 -0500 @@ -267,9 +267,10 @@ echo " -h, --help This help" echo " -i, --install Install package after successful build" echo " -j <jobs> Set MAKEFLAGS to \"-j<jobs>\" before building" + echo " -k, --keepdocs Keep doc and info directories" echo " -L, --log Log package build process" echo " -m, --nocolor Disable colorized output messages" - echo " -n, --nostrip Do not strip binaries/libraries" + echo " -n, --nostrip Do not strip symbols from binaries/libraries" echo " -o, --nobuild Download and extract files only" echo " -p <buildscript> Use an alternate build script (instead of '$BUILDSCRIPT')" echo " -r, --rmdeps Remove installed dependencies after a successful build" @@ -314,6 +315,7 @@ --noextract) NOEXTRACT=1 ;; --install) INSTALL=1 ;; --force) FORCE=1 ;; + --keepdocs) KEEPDOCS=1 ;; --nostrip) NOSTRIP=1 ;; --nobuild) NOBUILD=1 ;; --nocolor) USE_COLOR="n" ;; @@ -329,7 +331,7 @@ exit 1 ;; -*) - while getopts "bBcCdefghij:Lmnop:rsSw:-" opt; do + while getopts "bBcCdefghij:kLmnop:rsSw:-" opt; do case $opt in b) DEP_SRC=1 ;; B) USE_CCACHE=0 ;; @@ -345,6 +347,7 @@ ;; i) INSTALL=1 ;; j) export MAKEFLAGS="-j$OPTARG" ;; + k) KEEPDOCS=1 ;; L) LOGGING=1 ;; m) USE_COLOR="n" ;; n) NOSTRIP=1 ;; @@ -694,7 +697,7 @@ fi # use distcc if requested -if [ "$DISTCC" = "y" ]; then +if [ "$USE_DISTCC" = "y" ]; then [ -d /usr/lib/distcc/bin ] && export PATH=/usr/lib/distcc/bin:$PATH fi @@ -785,13 +788,13 @@ fi # remove libtool (.la) files -if [ "`check_option NOLIBTOOL`" ]; then +if [ "`check_option NOLIBTOOL`" -a "$NOLIBTOOL" = "1" ]; then msg "Removing libtool .la files..." find pkg -type f -name "*.la" -exec rm -f -- '{}' \; fi # remove empty directories -if [ "`check_option NOEMPTYDIRS`" ]; then +if [ "`check_option NOEMPTYDIRS`" -a "$NOEMPTYDIRS" = "1" ]; then msg "Removing empty directories..." find pkg -mindepth 1 -type d -empty -exec rmdir {} \; fi

4 3

[pacman-dev] My first piece of mail and a contribution
by Daniel McGee 15 Nov '06

15 Nov '06

Hey, I was bored one night and didn't really want to do homework, so I threw this together: a man page specifically for PKGBUILD, and in section 5 as I believe system file manpages should be. It incorporates variables at the top that makes setting distribution-specific wording much easier. Take it or leave it, but I thought I would at least put it out there. Dan ." 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 PKGBUILD 5 "Oct 25, 2006" "PKGBUILD version \*(VR" "\*(DS Files" .SH NAME PKGBUILD \- \*(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 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 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. \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 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 information on the package if needed. \fIdepends\fR and \fImakedepends\fR are bash arrays which define the dependencies of the package. Packages listed in \fImakedepends\fR are required only for building the package, and not for runtime. \fIdepends\fR is used to list runtime depends. To build the package using \fBmakepkg\fR, ALL dependencies must be satisfied. For \fBpacman\fR to install the package, all runtime depends must be satisfied. The \fIbackup\fR array specifies files that should be treated specially when removing or upgrading packages. See \fBHANDLING CONFIG FILES\fR in the \fIpacman\fR manpage for more information on this. The \fIsource()\fR array tells makepkg which files to download or extract before compiling begins. The \fImd5sums()\fR array provides md5sums for each of these files. These are used to validate the integrity of the source files. The \fIbuild\fR function is what actually does the work of putting the package together. Sometimes this is as simple as a configure, make, make install (to $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 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. .SS 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. .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 directive: install=pkgname.install The install script does not need to be specified in the \fIsource\fR array. A template install file is available in your ABS tree (/var/abs/install.proto). .SH OPTIONS AND 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 \*(DS's release. This allows package maintainers to make updates to the package's configure flags, for example. .TP .B pkgdesc This should be a brief description of the package and its functionality. ." Is this applicable below? .TP .B pkgdesc_localized \fI(array)\fR Array of the localized package descriptions. The format is the following: pkgdesc_localized=('xx_YY foo' 'xx_YY bar') .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 \fI(array)\fR This field specifies the license(s) that apply to the package. Commonly-used licenses are typically found in \fI/usr/share/licenses/common\fR. If you see the package's license there, simply reference it in the license field (eg, \fBlicense="GPL"\fR). If the package provides a license not found in \fI/usr/share/licenses/common\fR, then you should include the license in the package itself and set \fBlicense="custom"\fR or \fBlicense="custom:LicenseName"\fR. The license itself should be placed in a directory called \fI$startdir/pkg/usr/share/licenses/$pkgname\fR. If multiple licenses are applied, use the array form: \fBlicenses=('GPL' 'FDL')\fR .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\fR array. (eg, install=pkgname.install) ." Is this applicable below? .TP .B up2date This directive should contain a command that prints the current upstream stable version of the project. .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 file, unless they have a fully-qualified URL. .TP .B md5sums \fI(array)\fR 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 \fImd5sums\fR line from the bottom to an appropriate location. ." Is this applicable below? .TP .B signatures \fI(array)\fR 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: signatures=(${source[0]}.asc '') .TP .B groups \fI(array)\fR 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 archs \fI(array)\fR This array defines on which architectures the given package is available. .TP .B backup \fI(array)\fR A space-delimited array of filenames (without a preceding slash). The \fIbackup\fR 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\fR in the \fIpacman\fR manpage for more information. .TP .B depends \fI(array)\fR 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\fR, where <> is one of these three comparisons: \fB>=\fR (greater than equal to), \fB<=\fR (less than or equal to), or \fB=\fR (equal to). .TP .B makedepends \fI(array)\fR An array of packages that this package depends on to build, but not at runtime. Packages in this list should follow the same format as \fIdepends\fR. .TP .B conflicts \fI(array)\fR 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\fR except you cannot specify versions. .TP .B provides \fI(array)\fR An array of "virtual provisions" that this package provides. This allows a package to provide dependencies other than its own package name. For example, the kernel26beyond package can each provide 'kernel26' which allows packages to simply depend on 'kernel26' rather than "kernel26 OR kernel26beyond". .TP .B replaces \fI(array)\fR This is an array of packages that this package should replace, and can be used to handle renamed/combined packages. For example, if the j2re package gets renamed to jre, then subsequent 'pacman -Syu' calls will not pick up the upgrade, due to the differing package names. \fIreplaces\fR handles this. .TP .B options \fI(array)\fR 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\fR array. .RS .TP .B nostrip don't strip binaries/libraries. .TP .B keepdocs keep /usr/share/doc and /usr/share/info directories. .TP .B force force the package to be upgraded by --sysupgrade, even if it's an older version. .RE .SH EXAMPLE The following is an example PKGBUILD for the 'modutils' package. For more examples, look through the ABS tree. .nf # Maintainer: John Doe <johndoe(a)archlinux.org> pkgname=modutils pkgver=2.4.25 pkgrel=1 pkgdesc="Utilities for inserting modules in the linux kernel" url="http://www.kernel.org" makedepends=('bash' 'mawk') depends=('glibc' 'zlib') backup=(etc/modules.conf) source=(ftp://ftp.kernel.org/pub/linux/utils/kernel/$pkgname/v2.4/$pkgname-… \\ 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 .SH SEE ALSO .BR makepkg (8), .BR pacman (8) See the Arch Linux website at <http://www.archlinux.org> for more current information on the distribution, and <http://wiki.archlinux.org/index.php/Arch_Packaging_Standards> for recommendations on packaging standards. .SH AUTHORS Judd Vinet <jvinet(a)zeroflux.org> and the Frugalware developers <frugalware-devel(a)frugalware.org>

2 2