GNU bug report logs -
#13351
Dropping support for split '.info' files in mainline Automake
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#13351: Dropping support for split '.info' files in mainline Automake
which was filed against the automake package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 13351 <at> debbugs.gnu.org.
--
13351: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13351
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
On 01/12/2013 04:58 PM, Stefano Lattarini wrote:
> On 01/11/2013 10:55 PM, Paolo Bonzini wrote:
>> Il 03/01/2013 21:53, Stefano Lattarini ha scritto:
>>
>>> So I believe we could follow suit with Automake-NG (see commit dd603e21,
>>> <http://lists.gnu.org/archive/html/automake-ng/2012-08/msg00147.html>)
>>> and have Automake-generated makefiles pass the '--no-split' option
>>> unconditionally to makeinfo invocations (starting from Automake 1.14).
>>> This would allow some nice simplifications in our Texinfo recipe
>>> (exemplified by the Automake-NG patch referenced above), and offer an
>>> automatic fix for bug#12320.
>>>
>>> Another *very* good aspect of such a change is that it would be 100%
>>> transparent to the Automake users.
>>>
>>> Thoughts, opinions, objections?
>>
>> *This* is a change I support.
>>
>> Paolo
>>
> Glad to hear that. Since so far I've received only positive feedback, I
> will proceed to push the change to master in a couple of days if nobody
> objects.
>
Pushed now. I'm thus closing this bug report.
Regards,
Stefano
[Message part 3 (message/rfc822, inline)]
Severity: wishlist
[This is posted also to the automake and texinfo lists to ensure
a wider audience. Discussion should continue exclusively on the
bug-automake list, to avoid a cross-posting flood]
Automake-generated have for a long time supported "split" info files:
<http://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#Tag-and-Split-Files>
When I asked the rationale for this feature:
<http://lists.gnu.org/archive/html/texinfo-devel/2012-08/msg00015.html>
Karl Berry confirmed that the reason for its existence was indeed
"efficiency, especially memory size":
<http://lists.gnu.org/archive/html/texinfo-devel/2012-08/msg00024.html>
He also added that "The Elisp manual is one of the largest ones around.
Looks like it would be maybe 3.5mb as one file." Not in any way big by
modern standards.
OTOH, it appears that the use of split info files (at least in the way
Automake-generated rules have been handling them for a long time) can
cause real problems in some (admittedly quite corner-case) situations:
<http://thread.gmane.org/gmane.comp.parsers.bison.bugs/3963>
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12320>
So I believe we could follow suit with Automake-NG (see commit dd603e21,
<http://lists.gnu.org/archive/html/automake-ng/2012-08/msg00147.html>)
and have Automake-generated makefiles pass the '--no-split' option
unconditionally to makeinfo invocations (starting from Automake 1.14).
This would allow some nice simplifications in our Texinfo recipe
(exemplified by the Automake-NG patch referenced above), and offer an
automatic fix for bug#12320.
Another *very* good aspect of such a change is that it would be 100%
transparent to the Automake users.
Thoughts, opinions, objections?
Regards,
Stefano
This bug report was last modified 12 years and 124 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.