Re: Generated GDB documentation have colliding files on a case insensitive files system

Eli Zaretskii via Gdb-patches
2023-01-07T11:08:59Z

> Date: Sat, 7 Jan 2023 11:52:45 +0100
> CC: <gdb-patches@sourceware.org>
> From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
>
> On 2023-01-07 11:43, Eli Zaretskii wrote:
> >> Date: Sat, 7 Jan 2023 10:42:11 +0100
> >> CC: <gdb-patches@sourceware.org>
> >> From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
> >>
> >> Do you see any use of the ~214 redirect pages in the GDB context?
> >
> > Sorry, I don't understand the question. What do you mean by "see any
> > use" in this context?
>
> I was considering if the redirect files could simply be removed from the
> GDB documentation tree or if they are actually used for inter components
> references.

They are produced by makeinfo, and they are produced for a reason, no?

> I'm more or less trying to find the best solution for GDB.
>
> There is the possibility to rename one of the [qQ]MemTags anchors in the
> GDB documentation, but that will also include the alternative name in
> the redirect page and it would require all the @xref etc to be updated
> to the renamed anchor.
>
> Even if we get a solution merged in texinfo, it will take years for it
> to get activity used, and in the mean while, we are stuck with this
> issue in GDB.

I still don't want to make any conclusions until the Texinfo
discussion is completed. How do you know there's no solution with the
existing Texinfo versions?