Thanks for the report and looking into the code. There have been
previous reports relating to targets and conditionals, e.g.,
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=13940 (from 2013 ...)
and I think it's been mentioned in mail and elsewhere, too.
Updating the doc is no problem, thanks. But
Karl Berry writes:
> For GNU packages, dvi and pdf will normally be tested anyway as part of
> a release, due to the need to upload the new manuals to www.gnu.org.
> Perhaps we should remove dvi from there ... -k
Yes, as a start, could we drop linking to DVI manuals from gnulib's
gendocs_templat
Works for me, but don't we need to change the GNU coding standards to do
even that?
To my eyes, the coding standards only prescribe the existence of the
various dvi targets and variables. They don't say that making dvi is a
dependency of either check or installcheck. The distcheck target
On 2025-07-19 13:37, Karl Berry wrote:
However ... as far as I can tell, the problem in practice is Automake's
make distcheck depending on make dvi, not the mere existence of dvi
stuff in the Makefiles. So how about if we make that a no-op by default?
Works for me, but don't we need to change t
What kind of problems would attempting to build the DVI or PDF manual
really catch these days, which aren't already triggered by attempting to
make the *.info manual?
Building dvi/pdf definitely has a chance of catching errors,
since it's a complete different Texinfo implementation (te
The Standards reference
- Makefile targets 'dvi' and 'install-dvi',
- a variable 'dvidir',
- a configure option --dvidir.
All of these would have to be removed.
Although I have no particular initial objection to removing the dvi
stuff from standards.texi, I wouldn't want
Simon Josefsson wrote:
> Right. I would say that the days of the DVI and PS formats are probably
> long gone, and definitely as a default format. PDF has won.
DVI yes. PS has its use
1. as alternate format, at least in arXiv.org,
2. as easy-to-create vector graphics format.
> I tried to fin
Bruno Haible via Gnulib discussion list writes:
> Having said that, I would be in favour of retiring the DVI format from
> the GNU Coding Standards. The DVI format was commonplace in the 1990ies,
> but lost popularity to the PDF format starting 2008 (when PDF became an
> open standard). Nowadays,
Hello,
when you have a rule to generate ChangeLog inside a conditional, the
file is always added to am__DIST_COMMON, even when the conditional is
false. This leads to a failure to build the tarball, since the
ChangeLog file nor the rule to build it exist. I suspect it might be a
bug.
Following
