Hello.
Thank you for the great amount of work you put into the document.
You explain a lot of things in great detail on those 63 pages. Really
impressive.
I haven't read every single word in the document, I've just browsed
it, but I've found some issues which would need to be addressed:
Fixes automake bug https://bugs.gnu.org/54363.
There is no "aclocal" manual as it's all integrated into the automake
manual, so have all the help2man calls force automake as the manual.
* doc/local.mk: Use --info-page=automake for man pages.
---
doc/local.mk | 2 +-
1 file changed, 1
The attached patch.gz fixes the urls in automake.texi, adds checklinkx
to the contrib/ subdirectory, and a new target in doc/local.mk to invoke
it for rechecking.
Hearing no objection, I pushed this change (last night, belatedly
sending this mail, sorry) and am closing this bug. -k
Hi Stefano and all -- back on your report about broken urls from 2011 :) --
Date: Mon, 26 Dec 2011 22:03:50 +0100
Feeding the address of the on-line automake manual:
<http://www.gnu.org/software/automake/manual/automake.html>
to the W3C linkchecker:
<http://val
basis for understanding the material to follow. It is understood that
several sections in the introduction would be best presented as a general
introduction. However, Automake does not provide any insight into these
issues and any addressing of them in the Automake manual is scatter shot.
You
The subjects says it all, basically.
In section 3.3 The Uniform Naming Scheme I read:
``The current primary names are ‘PROGRAMS’, ‘LIBRARIES’, ‘LISP’,
‘PYTHON’, ‘JAVA’, ‘SCRIPTS’, ‘DATA’, ‘HEADERS’, ‘MANS’, and
‘TEXINFOS’. Some primaries also allow additional prefixes that
control
Hello automakers.
The automake manual, as build from latest git *master branch*, misses
release stats for the bugfix-releases 1.10.3 and 1.11.1 (see chapter 28
History, section 3 Release Statistics). Is this intentional, or
the result of an oversight?
P.S. The online Automake manual
Hi Stefano,
* Stefano Lattarini wrote on Tue, Jun 08, 2010 at 06:47:54PM CEST:
The automake manual, as build from latest git *master branch*, misses
release stats for the bugfix-releases 1.10.3 and 1.11.1 (see chapter 28
History, section 3 Release Statistics). Is this intentional
At Tuesday 08 June 2010, Ralf Wildenhues ralf.wildenh...@gmx.de
wrote:
I tend to update them lazily, i.e., shortly before a release is
made from the branch.
Ah, ok, Thanks for the information.
Regards,
Stefano
Hi Karl,
thanks for the quick review!
* Karl Berry wrote on Fri, Mar 27, 2009 at 11:26:24PM CET:
+* SUBDIRS vs DIST_SUBDIRS:: Two sets of directories
Probably a period after vs, to match the @subsection name (and because
this manual is (primarily?) in American English rather than
* Unfortunately, you cannot use periods, commas, colons or
parentheses within a node name; these confuse the Texinfo
processors. Perhaps this limitation will be removed some day, too.
Oh yeah :).
Well, the situation is that in practice, periods only cause trouble in
Hi Karl,
* Karl Berry wrote on Sat, Mar 28, 2009 at 11:25:26PM CET:
* Unfortunately, you cannot use periods, commas, colons or
parentheses within a node name; these confuse the Texinfo
processors. Perhaps this limitation will be removed some day, too.
Oh yeah :).
Hi Karl,
it took me the better part of a year to find enough energy to attack
http://thread.gmane.org/gmane.comp.sysutils.automake.bugs/4205.
* Karl Berry wrote on Wed, Jun 04, 2008 at 11:32:47PM CEST:
AIUI, the subsubheadings do not cause entries in the contents of the
PDF file. I'm
Hi Karl,
* Karl Berry wrote on Tue, Jun 03, 2008 at 07:26:20PM CEST:
I noticed automake.texi has many sectioning commands without nodes.
Mostly but not entirely @subsub-level entries.
This is quite unusual. It leads to some very long nodes. Was it a
deliberate decision?
I have no idea
AIUI, the subsubheadings do not cause entries in the contents of the
PDF file. I'm not sure I think that's better, though. Are there
other differences I overlooked?
Not in terms of formatting, but in terms of theory and how Texinfo is
typically used -- @section and the like should
I noticed automake.texi has many sectioning commands without nodes.
Mostly but not entirely @subsub-level entries.
This is quite unusual. It leads to some very long nodes. Was it a
deliberate decision? In cases like Install and Dist, I even venture to
say that it is a bug.
Anyway, if it is
Hello Reuben,
* Reuben Thomas wrote on Mon, Feb 04, 2008 at 12:50:45PM CET:
You mean appear newer, not appear older, as configure.ac is
lexically after configure. If configure.ac appeared older than
configure, then configure would not be rebuilt, spuriously or otherwise.
By the way,
Hello Bob,
Thanks for the report.
* Bob Wilkinson wrote on Mon, Jan 22, 2007 at 07:12:03PM CET:
I have been reading
http://www.gnu.org/software/automake/manual/html_mono/automake.html
You should instead be reading
http://sources.redhat.com/automake/automake.html
which
Hello Bobby,
* Bobby Jack wrote on Sat, Oct 28, 2006 at 12:16:49AM CEST:
Please accept my apologies if this is not the best
email address for this question.
It's just right. Thanks for reporting this!
Shouldn't the line [...]
This file is read by both autoconf (to create
configure.ac)
19 matches
Mail list logo
