[Rpm-maint] [patch] a couple of bug fixes

2007-08-06 Thread Ralf Corsepius
Hi, The patch below contains a couple of minor bug fixes, which are supposed to render currently non-buildable test programs buildable again. Ralf diff -r 425cce5ee453 rpmdb/tdbi.c --- a/rpmdb/tdbi.c Sun Aug 05 11:30:55 2007 +0300 +++ b/rpmdb/tdbi.c Mon Aug 06 09:36:34 2007 +0200 @@ -25,7 +25,7

[Rpm-maint] [patch] Use MKDIR_P

2007-08-06 Thread Ralf Corsepius
... and the next patch: It addresses 2 related issues * $(mkinstalldirs) in Makefile.ams is an anachronism. Modern Makefile.ams should use $(MKDIR_P) instead. * There is one direct call to mkdir -p inside of the toplevel Makefile.am - mkdir -p is non-portable. Portable Makefile.ams should use

Re: [Rpm-maint] [patch] a couple of bug fixes

2007-08-06 Thread Panu Matilainen
On Mon, 6 Aug 2007, Ralf Corsepius wrote: Hi, The patch below contains a couple of minor bug fixes, which are supposed to render currently non-buildable test programs buildable again. This + MKDIR_P and python patches all applied, thanks. Regarding the test-stuff: much (almost all?) of them

Re: [Rpm-maint] Re: RPM database on NFS root

2007-08-06 Thread Panu Matilainen
On Sun, 5 Aug 2007, Axel Thimm wrote: Hi, On Sat, Jul 21, 2007 at 07:24:36AM +, Panu Matilainen wrote: On Fri, 20 Jul 2007, Mark Hatle wrote: Jeremy Sanders wrote: Are there any plans to be able to host an RPM database over NFS? See

Re: [Rpm-maint] The description about option '--dump' in manpage is wrong

2007-08-06 Thread Panu Matilainen
On Thu, 2 Aug 2007, Yu Zhiguo wrote: Hello everybody, I find a bug in the latest rpm release(rpm-4.4.2.1 from http://www.rpm.org): The description about option '--dump' in manpage is wrong. The manpage says, This option must be used with at least one of -l, -c, -d., but in fact,

Re: [Rpm-maint] [patch] a couple of bug fixes

2007-08-06 Thread Ralf Corsepius
On Mon, 2007-08-06 at 12:17 +0300, Panu Matilainen wrote: On Mon, 6 Aug 2007, Ralf Corsepius wrote: Hi, The patch below contains a couple of minor bug fixes, which are supposed to render currently non-buildable test programs buildable again. This + MKDIR_P and python patches all

Re: [Rpm-maint] [patch] a couple of bug fixes

2007-08-06 Thread Panu Matilainen
On Mon, 6 Aug 2007, Ralf Corsepius wrote: On Mon, 2007-08-06 at 12:17 +0300, Panu Matilainen wrote: On Mon, 6 Aug 2007, Ralf Corsepius wrote: Hi, The patch below contains a couple of minor bug fixes, which are supposed to render currently non-buildable test programs buildable again. This

[Rpm-maint] [patch] Use PACKAGE_BUGREPORT

2007-08-06 Thread Ralf Corsepius
.. and yet another one: Use PACKAGE_BUGREPORT in rpmrc.c's error messages. Background: autoconf supplies a define (PACKAGE_BUGREPORT) which can be used to provide an email-address for bug reporting. So far, rpmrc.c sources used a hard-coded addresses instead. This had caused i18n'ed strings

Re: [Rpm-maint] [patch] Use PACKAGE_BUGREPORT

2007-08-06 Thread Panu Matilainen
On Mon, 6 Aug 2007, Ralf Corsepius wrote: .. and yet another one: Use PACKAGE_BUGREPORT in rpmrc.c's error messages. Background: autoconf supplies a define (PACKAGE_BUGREPORT) which can be used to provide an email-address for bug reporting. So far, rpmrc.c sources used a hard-coded addresses

[Rpm-maint] [patch] rpm is not a cross-tool

2007-08-06 Thread Ralf Corsepius
... today's flood continues ... The patch below removes AC_CANONICAL_TARGET from configure.ac and changes $target to $host. Background: AC_CANONICAL_TARGET is supposed to take the target of a cross-tool, not the target of cross-compiling a package (== a configure script's --host). Older

Re: [Rpm-maint] [patch] rpm is not a cross-tool

2007-08-06 Thread Mark Hatle
Umm... yes it is. I use RPM to cross-compile software ever day. I also cross compile RPM from one target to another routinely. You need to keep the $target references or you will make the rpm.org version of RPM unable to be cross compiled. --Mark Ralf Corsepius wrote: ... today's flood

Re: [Rpm-maint] [patch] rpm is not a cross-tool

2007-08-06 Thread Ralf Corsepius
On Mon, 2007-08-06 at 09:02 -0500, Mark Hatle wrote: Umm... yes it is. I use RPM to cross-compile software ever day. I also cross compile RPM from one target to another routinely. You need to keep the $target references or you will make the rpm.org version of RPM unable to be cross

Re: [Rpm-maint] [patch] rpm is not a cross-tool

2007-08-06 Thread Mark Hatle
Ralf Corsepius wrote: On Mon, 2007-08-06 at 09:02 -0500, Mark Hatle wrote: Umm... yes it is. I use RPM to cross-compile software ever day. I also cross compile RPM from one target to another routinely. You need to keep the $target references or you will make the rpm.org version of RPM

Re: [Rpm-maint] [patch] rpm is not a cross-tool

2007-08-06 Thread Ralf Corsepius
On Mon, 2007-08-06 at 09:26 -0500, Mark Hatle wrote: Ralf Corsepius wrote: On Mon, 2007-08-06 at 09:02 -0500, Mark Hatle wrote: Umm... yes it is. I use RPM to cross-compile software ever day. I also cross compile RPM from one target to another routinely. You need to keep the $target

Re: [Rpm-maint] [patch] rpm is not a cross-tool

2007-08-06 Thread Mark Hatle
The easiest way to check this. (Conceptually.. tailor to suit) On a non-linux host, such as solairs, configure to run on a linux host. If you following the paths through configure, you'll see it checks and hardcodes values based on the settings. I'm not an autoconf expert so I'll leave which