--- Begin Message ---
Subject: |
texinfo: could automake start using the '--tidy' option in its dvi and pdf rules? |
Date: |
Sun, 01 Apr 2012 14:30:34 +0200 |
Severity: wishlist
thanks
Hello everybody.
Reading the texi2dvi manpage, I've stumbled on this interesting bit of
information:
--tidy: compile in a local *.t2d directory, where the auxiliary files are
left. Output files are copied back to the original file.
...
Using the `tidy' mode brings several advantages:
- the current directory is not cluttered with plethora of temporary
files.
- clutter can be even reduced using --build-dir=dir: all the *.t2d
directories are stored there.
- if the compilation fails, the previous state of the output file is
preserved.
- PDF and DVI compilation are kept in separate subdirectories preventing
any possibility of auxiliary file incompatibility.
I think it would be nice if automake started to use the '--tidy' option of
texi2vi in its PDF and DVI generation from .texi files.
WDYT? Most importantly, is the '--tidy' option supported by all recently-ish
Texinfo releases, or has it been introduced too recently to mandate its use
in Automake-generated recipes?
Regards,
Stefano
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#11146: texinfo: could automake start using the '--tidy' option in its dvi and pdf rules? |
Date: |
Mon, 25 Jun 2012 12:01:08 +0200 |
On 04/04/2012 11:45 AM, Stefano Lattarini wrote:
>
>> I'll thus apply to two attached patches to master in a couple of days
>> if there is no objection.
>>
> Pushed now.
>
And the proposal for using '--tidy' in Automake 1.13 has been (basically)
implemented as part of this commit:
<http://git.savannah.gnu.org/cgit/automake.git/commit/?id=205c7572>
Actually, we ended up using per-manual and per-format '--build-dir' options, to
work around a bug still present in Texinfo 4.13 (but fixed in CVS Texinfo) that
could cause racy failures in parallel builds; but the effect of such option is
similar to the one we wanted to obtain using '--tidy'. The commit message of
that change should explain in more details.
I'm thus closing this bug report.
Regards,
Stefano
--- End Message ---