bug#7656: MANS primary accepts too many prefixes.

2010-12-17 Thread Stefano Lattarini
On Friday 17 December 2010, Ralf Wildenhues wrote: * Stefano Lattarini wrote on Thu, Dec 16, 2010 at 10:51:15PM CET: Currently, the MANS primary accept *all* the standard automake builtin prefix dirs (from lib and bin to pkglibexec and sysconf). IMHO it should accept only man and

bug#7657: TEXINFOS primary accepts too many prefixes.

2010-12-17 Thread Stefano Lattarini
On Friday 17 December 2010, Ralf Wildenhues wrote: * Stefano Lattarini wrote on Thu, Dec 16, 2010 at 10:52:10PM CET: Currently, the TEXINFOS primary accept *all* the standard automake builtin prefix dirs (from `lib' and `bin' to `pkglibexec' and `sysconf'). IMHO it should accept only

bug#7661: docs: typo in documentation about python extension modules?

2010-12-17 Thread Stefano Lattarini
In the section 10.5 Python of the manual, there is this example, which seems wrong (but I'm not sure, that's why I'm asking): pyexecdir This is the directory where Python extension modules (shared libraries) should be installed. An extension module written in C could be

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

2010-12-17 Thread Stefano Lattarini
tags 7379 wontfix close 7379 thanks On Friday 17 December 2010, Behdad Esfahbod wrote: On 12/16/10 18:19, Stefano Lattarini wrote: Given this rationale, would it be ok to close this bug now? Yes, as far as I'm concerned. behdad I'm closing the bug then. I'm also tagging it as wontfix,

bug#7647: Diagnose invalid primary/directory combinations

2010-12-17 Thread Stefano Lattarini
On Wednesday 15 December 2010, Ralf Wildenhues wrote: Hello, and dropping automake@, * Stefano Lattarini wrote on Wed, Dec 15, 2010 at 12:27:43PM CET: The list in `%standard_prefix' is used only for diagnosing invalid primary/directory combinations, such as `data_PROGRAMS' or

bug#7670: About make implementations that don't chain implicit rules

2010-12-17 Thread Stefano Lattarini
Severity: wishlist Hello automakers. Currently, automake is quite smart in catching and taking into account possible chaining of implicit rules. Here is a quite extensive example: $ cat Makefile.am 'END' bin_PROGRAMS = foo foo_SOURCES = foo.e .e.d: (echo 'int main() {' cat

bug#7671: Presetting various *CLEANFILES variables

2010-12-17 Thread Behdad Esfahbod
Hi, Currently, automake doesn't set any of the various *CLEANFILES variables. Since the += syntax is not portable when the variables are not initialized (and causes an automake warning), this leaves no option for Makefile.am snippets from various tools other than using the *clean-local targets to

bug#7661: docs: typo in documentation about python extension modules?

2010-12-17 Thread Ralf Wildenhues
* Stefano Lattarini wrote on Fri, Dec 17, 2010 at 02:51:12PM CET: pyexec_LTLIBRARIES = quaternion.la quaternion_SOURCES = quaternion.c support.c support.h quaternion_la_LDFLAGS = -avoid-version -module Shouldn't `quaternion_la_SOURCES' be used instead of