[FYI] docs, news: document planned removal of obsolete macros and features

* NEWS (Future backward-incompatibilities): Document planned removal of several superseded and/or obsoleted macros, of the $(mkdir_p) variable and @mkdir_p@ substitution, and of the support for the two- or three-arguments invocation forms of AM_INIT_AUTOMAKE. * doc/automake.texi: Likewise. --- NEW

Re: [FYI] {master} maint: assume 'test -x' is portable

On 02/23/2012 11:49 PM, Harlan Stenn wrote: > Eric wrote: >> The autoconf manual still recommends: >> >> Do not use @samp{test -x}, because 4.3BSD does not >> have it. >> >> Is this still an issue? Or should we be updating the autoconf manual? > > I remember this biting me within the last ~4 year

[FYI] {master} docs: remove reference to lzma support, it has been removed

Support for lzma compression in distribution tarball has been removed in commit 'v1.11-1674-g02e9072' of 01-01-2012, "dist: remove support for lzma (superseded by xz and lzip)", but was still documented in the manual. * doc/automake.texi: Remove references to the 'dist-lzma' option and to the lzma

Re: [FYI] {master} maint: assume 'test -x' is portable

It's been Quite Some Time since I've had to deal with 4.3BSD, or any host with a "test -x" problem, so I suggest the following patch to the Autoconf manual: diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 607d8dc..443ec07 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -18125,9

Re: [FYI] {master} maint: assume 'test -x' is portable

Eric wrote: > The autoconf manual still recommends: > > Do not use @samp{test -x}, because 4.3BSD does not > have it. > > Is this still an issue? Or should we be updating the autoconf manual? I remember this biting me within the last ~4 years' time. I don't know if it's still an issue or not,

Re: [FYI] {master} maint: assume 'test -x' is portable

On 02/23/2012 02:48 PM, Stefano Lattarini wrote: > * lib/Makefile.am (installcheck-local): To verify that the installed > scripts are actually executable, simply use 'test -x', instead of > resorting to perl and its '-x' file operator. Today, 'test -x' > should today be portable to any non-museum

[FYI] {master} cosmetics: fixlet in comment in automake

* automake.in ($configure_dist_common): In the associated comment, refer to scanning of 'configure.ac', not 'configure.in'. --- automake.in |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/automake.in b/automake.in index 13e65df..9110e52 100644 --- a/automake.in +++ b/auto

[FYI] {master} maint: assume 'test -x' is portable

* lib/Makefile.am (installcheck-local): To verify that the installed scripts are actually executable, simply use 'test -x', instead of resorting to perl and its '-x' file operator. Today, 'test -x' should today be portable to any non-museum system. Since we are at it, improve diagnostic in case o

[FYI] {master} deptrack: avoid few forks in configure (minor optimization)

* m4/depend.m4 (_AM_DEPENDENCIES): Use 'echo > file' instead of 'touch file' to ensure the creation of a dummy file. Adjust the comment that explains why we can't merely use ': > file': the problem this latter idiom tickles is present also with Solaris 10 /bin/sh, not merely with Solaris 8 /bin/sh

[FYI] {master} maintcheck: remove obsolete check

* syntax-check.mk (sc_perl_local_no_parens): Remove, we don't even allow the use of local but for the '$_' and '$~' special variables. (syntax_check_rules): Adjust. --- syntax-checks.mk |8 1 files changed, 0 insertions(+), 8 deletions(-) diff --git a/syntax-checks.mk b/syntax-checks

[FYI] {master} news: update w.r.t. change in quoting format

* NEWS (New in 1.11.1a): State that we prefer to quote 'like this' or "like this" rather than `like this', as according to the new GCS recommendations. --- NEWS |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/NEWS b/NEWS index 53a2f46..b5b184e 100644 --- a/NEWS +++ b/NE

Re: [PATCH] tests: prefer 'configure.ac' over 'configure.in'

On 02/23/2012 09:24 PM, p...@lysator.liu.se wrote: > >> Which FAILs exactly? I've experienced none (but then again, the >> MinGW/MSYS specifc tests are always skipped on my systems). Also, >> I've added a new maintainer check 'sc_tests_no_configure_in' to >> ensure we don't have unwarranted uses

Re: [PATCH] tests: prefer 'configure.ac' over 'configure.in'

> Hi Peter. > > On 02/22/2012 08:31 PM, p...@lysator.liu.se wrote: >>> On 02/21/2012 09:56 PM, Stefano Lattarini wrote: With this change, our testsuite now uses 'configure.ac' as the name for the typical autoconf input, instead of the obsolescent 'configure.in' (which has been deprec

[FYI] {master} hacking: update advice w.r.t. release process

* HACKING: Don't describe the obsolete 'git-release' target anymore. Instead, document the new and improved targets 'git-tag-release' and 'git-upload-release' (introduced in commit v1.11-674-gaf5f939 of 25-01-2012, "release: revamp rules to tag and upload the releases"). --- HACKING | 19 +++

[FYI] {master} hacking: do not quote `like this', as per GCS recommendation

* HACKING: Quote 'like this' or "like this", not `like this'. This is done for consistency with the new recommendations in the GNU Coding Standards, and because I've come to actually prefer the '...' and "..." quoting format over the `...' one. --- HACKING | 38 +++--

[PATCH] {master} am: do not quote `like this', as per GCS recommendation

This patch converts the automake-provided '*.am' fragments, and related files, to the use of new quoting format 'like this' or "like this" rather than `like this'. This is done for consistency with the new recommendations in the GNU Coding Standards, and, well, because I've come to actually like t

[PATCH] tests: looks for GNU compilers at configure time (was: Re: bug#10859: AC_PROG_CC mistaken clang for GCC)

[Dropping bug-autoconf] Reference: On 02/21/2012 10:52 PM, Stefano Lattarini wrote: > > Now that we have identified the problem, fixing it shouldn't be too difficult; > I will follow-up in the next days with a patch. > Here it is (for master).