bug#7379: On the fix for CVE-2009-4029 Automake security fix for 'make dist*'

2010-11-13 Thread Ralf Wildenhues
[ Thanks Glenn for rerouting the bug report! ] Hi Behdad, From: Behdad Esfahbod Subject: On the fix for CVE-2009-4029 Automake security fix for 'make dist*' Date: Thu, 11 Nov 2010 16:17:22 -0500 I recently read about the fix for the chmod 777 issue. Just wanted to note that it may be

[PATCH] {master} Deprecate obsoleted macro AM_WITH_REGEX.

2010-11-13 Thread Stefano Lattarini
OK for master? * m4/regex.m4: Document the `AM_WITH_REGEX' macro as obsoleted, and tell that it should be removed two years from now. (AM_WITH_REGEX): Raise an m4-time warning of the obsolete category when this macro is used. * doc/automake.texi (Public Macros): Move description of

Re: [PATCH] {master} Deprecate obsoleted macro AM_WITH_REGEX.

2010-11-13 Thread Ralf Wildenhues
* Stefano Lattarini wrote on Sat, Nov 13, 2010 at 12:32:49PM CET: * m4/regex.m4: Document the `AM_WITH_REGEX' macro as obsoleted, I think technically obsolete is right here, without trailing d. and tell that it should be removed two years from now. s/tell/state/ (AM_WITH_REGEX): Raise an

Re: [PATCH 1/3] aclocal: handle ACLOCAL_PATH environment variable

2010-11-13 Thread Ralf Wildenhues
* Paolo Bonzini wrote on Tue, Nov 09, 2010 at 08:14:38PM CET: This updated patch passes the tests suggested by Stefano. Considering that Automake will rarely if ever be invoked from outside, MSYS, I stuck with the colon as the sole separator for ACLOCAL_PATH. The test suites leaves the

Re: [PATCH] {master} Deprecate obsoleted macro AM_WITH_REGEX.

2010-11-13 Thread Stefano Lattarini
On Saturday 13 November 2010, Ralf Wildenhues wrote: * Stefano Lattarini wrote on Sat, Nov 13, 2010 at 12:32:49PM CET: * m4/regex.m4: Document the `AM_WITH_REGEX' macro as obsoleted, I think technically obsolete is right here, without trailing d. OK. All instances fixed. and tell that it

Re: [PATCH] {master} Deprecate obsoleted macro AM_WITH_REGEX.

2010-11-13 Thread Ralf Wildenhues
* Stefano Lattarini wrote on Sat, Nov 13, 2010 at 01:39:04PM CET: On Saturday 13 November 2010, Ralf Wildenhues wrote: * Stefano Lattarini wrote on Sat, Nov 13, 2010 at 12:32:49PM CET: Is rx a package? Where did you find traces to it? There was this in automake.texi: @cindex rx package

Re: User extensions

2010-11-13 Thread Pippijn van Steenhoven
On Mon, Nov 01, 2010 at 08:18:44PM +0100, Ralf Wildenhues wrote: Ideally, I would like to see testsuite coverage for each code path (branch coverage) for new code. I understand that only Stefano is able to produce this in reasonable amount of time, so whatever you guys can manage is better

Re: [PATCH] {master} Deprecate obsoleted macro AM_WITH_REGEX.

2010-11-13 Thread Stefano Lattarini
On Saturday 13 November 2010, Ralf Wildenhues wrote: * Stefano Lattarini wrote on Sat, Nov 13, 2010 at 01:39:04PM CET: On Saturday 13 November 2010, Ralf Wildenhues wrote: * Stefano Lattarini wrote on Sat, Nov 13, 2010 at 12:32:49PM CET: Is rx a package? Where did you find traces to it?

Re: How to structure a GNU scientific project

2010-11-13 Thread Ralf Wildenhues
Hello Luke, you somehow managed to send mail to the automake list without the list address in Cc:, let's fix that. * Luke wrote on Mon, Nov 08, 2010 at 07:36:13PM CET: I'm trying to organize the directory and file structure of my project and figure out how everything should be installed in a

Re: User extensions

2010-11-13 Thread Pippijn van Steenhoven
On Mon, Nov 01, 2010 at 08:18:44PM +0100, Ralf Wildenhues wrote: Ideally, I would like to see testsuite coverage for each code path (branch coverage) for new code. I understand that only Stefano is able to produce this in reasonable amount of time, so whatever you guys can manage is better

ACLOCAL best practice

2010-11-13 Thread Ryan Lortie
Hello, We use ACLOCAL_FLAGS in the GNOME project to specify the include directories for when we are installing into unusual prefixes. For example, say I have a GNOME setup in /home/desrt/local. If I install glib, it includes gsettings.m4 which gets installed into

Re: ACLOCAL best practice

2010-11-13 Thread Stefano Lattarini
On Saturday 13 November 2010, Ryan Lortie wrote: Hello, Hello Ryan. Just a quick partial reply ... [CUT] In my opinion, this is an argument for why ACLOCAL_FLAGS (or at least some ACLOCAL_PATH environment variable) Supporting ACLOCAL_PATH is a good idea IMO -- and the nice thing about it is

builddir

2010-11-13 Thread Russell Shaw
Hi, In a Makefile.in generated by automake 1.9.6, it defines top_builddir ok, but builddir is used but not defined in there. This causes problems, because the automake manual says: — Variable: builddir Rigorously equal to ‘.’. Added for symmetry only.