Hello Behdad, and thanks for the bug report,
* Behdad Esfahbod wrote on Sat, Dec 18, 2010 at 01:55:22AM CET:
> If instead automake was changed to always pre-initialize *CLEANFILES
> variables, all snippets could just append to do variables and my git.mk
> snippet would be more generic and much mor
* Stefano Lattarini wrote on Sat, Dec 18, 2010 at 03:12:17PM CET:
> Currently, the strictness-related options specified with AM_INIT_AUTOMAKE
> in configure.ac and with AUTOMAKE_OPTIONS in Makefile.am win over those
> specified on the command line:
> While this behaviour might have had its histori
* Stefano Lattarini wrote on Fri, Dec 17, 2010 at 07:52:29PM CET:
> With automake >= 1.10, foreign *after* -Wall in AM_INIT_AUTOMAKE turns
> off portability warnings.
> While the current behaviour is due to various historical and implementation
> reasons, IMHO it is counter-intuitive and somewhat
* Stefano Lattarini wrote on Fri, Dec 17, 2010 at 12:19:40PM CET:
> On Friday 17 December 2010, Ralf Wildenhues wrote:
> > For example, I can easily imagine a package having normal texinfo
> > manuals, but also a developer's manual that maybe should end up
> > in an internal directory elsewhere (or
* Stefano Lattarini wrote on Fri, Dec 17, 2010 at 11:52:17PM CET:
> Currently, automake is quite smart in catching and taking into account
> possible chaining of implicit rules.
[...]
> And here comes the problem. While the above example works correctly for
> at least GNU make (tested with versio
Hi Stefano,
Thanks for the prompt reply.
On 12/18/10 05:02, Stefano Lattarini wrote:
> Note that the *CLEANFILES variables cannot be used to remove directories,
> so, for your approach to be really useful in all cases (i.e. also be able
> to git-ignore generated directories easily), a similar se
