Re: Fix doc index name on Windows

[Pedro Alves <pedro at codesourcery dot com>]

On Friday 26 November 2010 12:54:40, Eli Zaretskii wrote:
> > If such code is only triggerable on some hosts only, then IMO it
> > is broken, because the resulting files will not be movable between
> > hosts (e.g., generate on Unix, unpack on Windows/NTFS/FAT/Samba, whatnot).
> 
> IMO, "broken" is an exaggeration.

Maybe.  The emphasis should have been on "triggerable".  I don't
think one should have to build makeinfo for the host -- the build
machine's makeinfo should be useable in canadian crosses to build
the host's documentation.  Like the build machine's coreutils,
findutils, etc. are.

> How many tools did you see that
> care about having their files produced on Unix be compatible with
> NTFS?  How many maintainers of GNU packages do you know who would even
> consider a possibility of inserting NTFS-related limitations into
> their codebase?

Many.  I didn't mean that the "limitation" should be be added by
default, but as an option.

> > Is there a way to force that behaviour with a makeinfo command line
> > switch or something of the sort?
> 
> Not that I know of.  No one has ever asked for that, AFAIK.  But it
> should be trivial to add such a switch, now that I pointed to the code
> which does that.

Thanks.

Note that FWIW, I'd be perfectly happy with a change to our manual
to work around the issue.  We carry a similar patch in our tree.

-- 
Pedro Alves