- Pacman-dev - lists.archlinux.org

[pacman-dev] alpm_option_set_logcb(), an example of usage
by Imanol Celaya 15 Aug '08

15 Aug '08

Hi, I'm developing pyalpm at the moment(new codebase, not related to 2005 pyalpm) and I don't really see any example of usage of alpm_option_set_logcb() on pacman.c file there is alpm_option_set_logcb(cb_log); but I can't find where is cb_log declared, so I have no clue about what does that function do(as I haven't neither found where is the actual code of that function, only that is declared on alpm.h)

4 6

Re: [pacman-dev] Splitting packages with makepkg
by Marc - A. Dahlhaus [ Administration | Westermann GmbH ] 15 Aug '08

15 Aug '08

Hello, Am Freitag, den 15.08.2008, 12:57 +1000 schrieb Allan McRae: > Henning Garus wrote: > > Now my (maybe) more useful comments: > > > > This looks very much like the PKGBUILD I already had in my head after > > reading the other threads and thinking about splitting packages. While > > thinking I became unsure about two things: > > > > 1) Is one build function enough? In an older thread someone (Aaron I > > think) talked about building packages with different configurations > > from one packagebuild. I am not sure you can do this with one build > > function. What you could do, is using the package functions to do this, > > this would go against the "minimal fakeroot usage" thing, but is > > probably sufficent for something rather uncommon. An alternative would > > be, checking for build_pkgname functions and calling them if they are > > defined. > > > > > Two build functions sounds like it would require two install functions > (as each package would probably have to add a conflict to the other) > which is really two PKGBUILDs. I am not against adding this at the same > time but I would need to be convinced with a (useful) real world example > here. How about this: A "build_${pkgname}" function should be executed for every (including the first) package (if exists for the first of course) after executing the "build" function (if it exists) before the execution of any other "build_${pkgname}" function without executing the packaging of contents "build" may have written to ${startdir}/pkg: (0. -> build) if exist 1. -> build_pkg1 2. -> pack ${startdir}/pkg_pkg1 3. -> build_pkg2 4. -> pack ${startdir}/pkg_pkg2 If there is no build_pkg1 function: 1. -> build 2. -> pack ${startdir}/pkg 3. -> build_pkg2 4. -> pack ${startdir}/pkg_pkg2 That way it is up to the packager if a main build function should be used to build everything and install things in separate functions to override eg. depends or just use separated build functions for every split-package. A real world example would be php5 which could be build for cli, cgi and mod_php usage for apache2. Also many modules for php5 could be packed up separately to minimize the depends for the main packages down to the ones really needed for basic operation. I'll try to adapt my php PKGBUILD to the proposed format over the weekend. > > 2) This is a bit implementation specific, but I think it is important. > > Is there any way, except parsing the PKGBUILD file, to get the contents > > of all depends arrays, to check the depends before building the package? > > If not, overriding depends could be problematic. > > > > As Xavier pointed out, I think that there would a big use of makedepends > and overriding of depends in the individual package functions. In fact, > I am not sure what the depends array at the top of the PKGBUILD actually > means with split packages... I would expect that the global array should represent all needed dependencies to build every spilt-package (it would be the easiest way to get a working "makepkg -s"). OT: I found out that export have to be used to override vars inside of functions that are already defined outside. It could be a bash configuration problem here on my box but i hope someone can verify this behavior. Marc

1 0

[pacman-dev] Splitting packages with makepkg
by Allan McRae 15 Aug '08

15 Aug '08

Hi all, Now that pacman 3.2 is out the door and the initial bug fixes appear done, I am going to work on adding the package splitting feature to makepkg. So the time has come for some input on the prototype PKGBUILD for splitting packages again. We discussed this a couple of months ago on this list (http://archlinux.org/pipermail/pacman-dev/2008-June/012123.html) From that discussion I have come up with a PKGBUILD prototype which I like (prototype 1 at http://dev.archlinux.org/~allan/splitpkg.html) which is inspired by the KDEMod method but has a few significant differences. This is a call for comments or other prototypes to implement this function. Some "rules" to help us all with this: 1) If submitting a new idea, attach a complete prototype (based on the one distributed with pacman) so we can see all details of how the packaging is done. Add notes if necessary. Point out the advantages of your method. 2) Note that the ability to separate the building and packaging stages of a PKGBUILD is going to be added to makepkg so that fakeroot is used for the smallest amount of time. Any new prototype should account for this. 3) No comments about how splitting packages is bad and this will be the ruin of Arch. Arch does not favor package splitting in its main repos and this will not change that fact. Allan

3 5

[pacman-dev] [PATCH] Add autotools magic for pactests
by Henning Garus 14 Aug '08

14 Aug '08

Added a Makefile.am for the pactest/tests dir. This is a blatant ripoff of scripts/Makefile.am, which replaces predefined expressions in NAME.py.in pactests with configure variables. This can be used to write pactests which consider compile time options. Signed-off-by: Henning Garus <henning.garus(a)gmail.com> --- Makefile.am | 2 +- configure.ac | 1 + pactest/tests/Makefile.am | 19 +++++++++++++++++++ 3 files changed, 21 insertions(+), 1 deletions(-) create mode 100644 pactest/tests/Makefile.am diff --git a/Makefile.am b/Makefile.am index ea3b0e0..4f2ea83 100644 --- a/Makefile.am +++ b/Makefile.am @@ -1,4 +1,4 @@ -SUBDIRS = lib/libalpm src/util src/pacman scripts etc po pactest contrib +SUBDIRS = lib/libalpm src/util src/pacman scripts etc po pactest pactest/tests contrib if WANT_DOC SUBDIRS += doc endif diff --git a/configure.ac b/configure.ac index 9f4209b..5c09e2e 100644 --- a/configure.ac +++ b/configure.ac @@ -342,6 +342,7 @@ doc/Makefile etc/Makefile po/Makefile.in pactest/Makefile +pactest/tests/Makefile contrib/Makefile Makefile ]) diff --git a/pactest/tests/Makefile.am b/pactest/tests/Makefile.am new file mode 100644 index 0000000..4590e3c --- /dev/null +++ b/pactest/tests/Makefile.am @@ -0,0 +1,19 @@ +CONFTESTS = $(patsubst %py.in,%py,$(wildcard *.py.in)) + +noinst_SCRIPTS = $(CONFTESTS) + +CLEANFILES = $(CONFTESTS) + +edit = sed \ + -e 's|@LIBS[@]|$(LIBS)|g' \ + -e 's|@configure_input[@]|Generated from $@.in; do not edit by hand.|g' + + +$(CONFTESTS): Makefile + rm -f $@ $@.tmp + test -f $(srcdir)/$@.in && $(edit) $(srcdir)/$@.in >$@.tmp || true + test -f $@.tmp || false + chmod a-w $@.tmp + mv $@.tmp $@ + +# vim:set ts=2 sw=2 noet: -- 1.5.6.5

1 0

[pacman-dev] minor issue in pacman.conf
by Xavier 13 Aug '08

13 Aug '08

Patch attached.

2 2

[pacman-dev] [PATCH] Treat info pages like man pages
by Allan McRae 12 Aug '08

12 Aug '08

As far a package building is concerned, info pages need to be treated in the same fashion as man pages in that they both can be compressed. This separates them from other forms of documentation and so it makes sense to make that distinction within makepkg. Signed-off-by: Allan McRae <allan(a)archlinux.org> --- doc/PKGBUILD.5.txt | 6 +++--- doc/makepkg.conf.5.txt | 6 +++--- etc/makepkg.conf.in | 2 +- scripts/makepkg.sh.in | 12 ++++++------ 4 files changed, 13 insertions(+), 13 deletions(-) diff --git a/doc/PKGBUILD.5.txt b/doc/PKGBUILD.5.txt index 0b1ce64..cf6eb23 100644 --- a/doc/PKGBUILD.5.txt +++ b/doc/PKGBUILD.5.txt @@ -181,8 +181,8 @@ similar to `$_basekernver`. disable this option. *docs*;; - Save doc and info directories. If you wish to delete doc and - info directories, specify `!docs` in the array. + Save doc directories. If you wish to delete doc directories, + specify `!docs` in the array. *libtool*;; Leave libtool (.la) files in packages. Specify `!libtool` to @@ -192,7 +192,7 @@ similar to `$_basekernver`. Leave empty directories in packages. *zipman*;; - Compress man pages with gzip. + Compress man and info pages with gzip. *ccache*;; Allow the use of ccache during build. More useful in its negative diff --git a/doc/makepkg.conf.5.txt b/doc/makepkg.conf.5.txt index 8b39c46..57b229f 100644 --- a/doc/makepkg.conf.5.txt +++ b/doc/makepkg.conf.5.txt @@ -110,8 +110,8 @@ Options option. *docs*;; - Save doc and info directories. If you wish to delete doc and info - directories, specify `!docs' in the array. + Save doc directories. If you wish to delete doc directories, specify + `!docs' in the array. *libtool*;; Leave libtool (.la) files in packages. Specify `!libtool' to remove @@ -121,7 +121,7 @@ Options Leave empty directories in packages. *zipman*;; - Compress man pages with gzip. + Compress man and info pages with gzip. **INTEGRITY_CHECK=(**check1 ...**)**:: File integrity checks to use. Multiple checks may be specified; this diff --git a/etc/makepkg.conf.in b/etc/makepkg.conf.in index 0241a8e..057f563 100644 --- a/etc/makepkg.conf.in +++ b/etc/makepkg.conf.in @@ -72,7 +72,7 @@ OPTIONS=(strip docs libtool emptydirs zipman) #-- File integrity checks to use. Valid: md5, sha1, sha256, sha384, sha512 INTEGRITY_CHECK=(md5) #-- Info and doc directories to remove (if option set correctly above) -DOC_DIRS=(usr/{,share/}{info,doc,gtk-doc} opt/*/{info,doc,gtk-doc}) +DOC_DIRS=(usr/{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc}) #-- Directories to be searched for the strip option (if option set correctly above) STRIP_DIRS=(bin lib sbin usr/{bin,lib,sbin,local/{bin,lib,sbin}} opt/*/{bin,lib,sbin}) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index c5dbed9..a665ba7 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -679,16 +679,16 @@ tidy_install() { msg "$(gettext "Tidying install...")" if [ "$(check_option docs)" = "n" ]; then - msg2 "$(gettext "Removing info/doc files...")" + msg2 "$(gettext "Removing doc files...")" #fix flyspray bug #5021 rm -rf ${DOC_DIRS[@]} fi if [ "$(check_option zipman)" = "y" ]; then - msg2 "$(gettext "Compressing man pages...")" + msg2 "$(gettext "Compressing man and info pages...")" local manpage mandirs ext file link hardlinks hl - mandirs="usr/man usr/share/man usr/local/man usr/local/share/man opt/*/man" - find ${mandirs} -type f 2>/dev/null | + mandirs=({usr{,/local}{,/share},opt/*}/{man,info}) + find ${mandirs[@]} -type f 2>/dev/null | while read manpage ; do # check file still exists (potentially compressed with hard link) if [ -f ${manpage} ]; then @@ -696,7 +696,7 @@ tidy_install() { file="${manpage##*/}" if [ "$ext" != "gz" -a "$ext" != "bz2" ]; then # update symlinks to this manpage - find ${mandirs} -lname "$file" 2>/dev/null | + find ${mandirs[@]} -lname "$file" 2>/dev/null | while read link ; do rm -f "$link" ln -sf "${file}.gz" "${link}.gz" @@ -704,7 +704,7 @@ tidy_install() { # find hard links and remove them # the '|| true' part keeps the script from bailing if find returned an # error, such as when one of the man directories doesn't exist - hardlinks="$(find ${mandirs} \! -name "$file" -samefile "$manpage" 2>/dev/null)" || true + hardlinks="$(find ${mandirs[@]} \! -name "$file" -samefile "$manpage" 2>/dev/null)" || true for hl in ${hardlinks}; do rm -f "${hl}"; done -- 1.5.6.5

1 0

[pacman-dev] sourcing /etc/profile and set -e bug in makepkg
by Allan McRae 11 Aug '08

11 Aug '08

So, despite me assuring Dan that nothing could possibly go wrong, the commit to source /etc/profile rather than individual files in /etc/profile.d (http://projects.archlinux.org/?p=pacman.git;a=commitdiff;h=0e0a8461) has caused a problem. See FS#11179 (http://bugs.archlinux.org/task/11179) for more details. Xavier and I are stuck as to what is actually causing this problem. The guilty script being sourced is /etc/bash_completion.d/modules and specifically the "type modules" statement at the top. What we don't understand is that this file is being sourced under both methods and why it is causing problems only with one. Even more confusing, the way it gets sourced in /etc/profile is essentially the way makepkg used to do it (loop over /etc/profile.d/* files). A work-around is to add "set +e" and "set -e" on either side of the "source /etc/profile" call. That is probably a good idea anyway as that sourcing should probably not inherit the "-e" property. But can anyone explain why we now need this? Very confused, Allan

2 3

[pacman-dev] Pacman only tries to resolve with the primary nameserver
by Teran McKinney 10 Aug '08

10 Aug '08

Hey, While revamping eleutherNet's ( http://eleuther.net ) DNS setup and giving it external IPv6 connectability, I found Pacman's sync server resolving method to be problematic during testing. Pacman 3.2.0 seems to only try the primary nameserver when resolving a server to sync to. The common (though not completely ideal) practice for using internal domains in VPNs is making the internal DNS server your primary and keeping your normal nameserver as secondary for resolving "real" domains after the VPN's DNS server fails to resolve the domain. Almost all applications will try to resolve through the whole nameserver list if there are no matches initially, but Pacman does not seem to.do this. Pacman is an awesome package manager, but having either optional or standard functionality for this would be nice. Thanks, Teran (sega01)

2 1

[pacman-dev] [PATCH] Fix segfault on x86_64 when using UseSyslog
by Dan McGee 10 Aug '08

10 Aug '08

Due to differences in handling va_list between i686 and x86_64, this bug can only be seen on x86_64. va_list usage is not allowed but we had been getting away with it. See http://lists.opensuse.org/opensuse-programming/2008-02/msg00005.html for details and explanation. This fixes FS#11096. Signed-off-by: Dan McGee <dan(a)archlinux.org> --- lib/libalpm/util.c | 11 +++++++++-- 1 files changed, 9 insertions(+), 2 deletions(-) diff --git a/lib/libalpm/util.c b/lib/libalpm/util.c index c38dfb5..2847db7 100644 --- a/lib/libalpm/util.c +++ b/lib/libalpm/util.c @@ -25,6 +25,7 @@ #include <stdio.h> #include <stdlib.h> +#include <stdarg.h> #include <string.h> #include <fcntl.h> #include <unistd.h> @@ -401,12 +402,18 @@ int _alpm_rmrf(const char *path) return(0); } -int _alpm_logaction(unsigned short usesyslog, FILE *f, const char *fmt, va_list args) +int _alpm_logaction(unsigned short usesyslog, FILE *f, + const char *fmt, va_list args) { int ret = 0; if(usesyslog) { - vsyslog(LOG_WARNING, fmt, args); + /* we can't use a va_list more than once, so we need to copy it + * so we can use the original when calling vfprintf below. */ + va_list args_syslog; + va_copy(args_syslog, args); + vsyslog(LOG_WARNING, fmt, args_syslog); + va_end(args_syslog); } if(f) { -- 1.5.6.5

4 4

Re: [pacman-dev] [arch-dev-public] [signoff] pacman 3.2.0
by Dan McGee 10 Aug '08

10 Aug '08

On Thu, Jul 31, 2008 at 2:01 AM, Eric Belanger <belanger(a)astro.umontreal.ca> wrote: > On Wed, 30 Jul 2008, Dan McGee wrote: > >> Pacman 3.2.0 is in testing for i686. Please signoff. Changes outlined >> here: http://projects.archlinux.org/?p=pacman.git;a=blob;f=NEWS >> > > When building mythbrowser, I noticed that makepkg now fails when there is an > '?' in the sources, e.g. > source=("http://www.mythtv.org/modules.php?name=Downloads&d_op=getit&lid=136&foo=/my…") > > Removing the double quotes and escaping the characters doesn't work. > > The error message: > > ==> ERROR: There is no agent set up to handle URLs. Check > /etc/makepkg.conf. > Aborting... > > Not a showstopper as the source can be downloaded maunally in the build dir. > I'll try to look into it further tomorrow. We have a regression here, and it is actually bigger than it looks at first sight. Can you file a bug report for this? Tracing the code shows that %o and %u are never even used right now, as they don't make it all the way through to the download stage. -Dan

9 20