public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra.loosemore@siemens.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: "Richard Biener" <richard.guenther@gmail.com>,
	"Andrew Pinski" <pinskia@gmail.com>,
	"Sandra Loosemore" <sandra@codesourcery.com>,
	"Arsen Arsenović" <arsen@aarsen.me>,
	"GCC Patches" <gcc-patches@gcc.gnu.org>,
	"Gerald Pfeifer" <gerald@pfeifer.com>,
	"Joseph Myers" <joseph@codesourcery.com>
Subject: Re: [PATCH v2 0/5] A small Texinfo refinement
Date: Fri, 10 Mar 2023 10:51:21 -0700	[thread overview]
Message-ID: <e45049c9-5042-13cd-ce0b-8bf0db8dca93@siemens.com> (raw)
In-Reply-To: <8B7A5370-059A-41E7-B809-B51CA964150E@googlemail.com>

On 3/10/23 01:50, Iain Sandoe wrote:
> Hi all,
> 
>> On 9 Mar 2023, at 23:35, Sandra Loosemore via Gcc-patches
>> <gcc-patches@gcc.gnu.org> wrote:
>> 
>> On 3/9/23 01:26, Richard Biener wrote:
>> 
>>> SLES 12 has texinfo 4.13a, SLES 15 has texinfo 6.5.  We still
>>> provide up-to-date GCC for SLES 12 but we can probably manage in
>>> some ways when the texinfo requirement gets bumped.
>> 
>> OK, this seems to be the oldest version anyone admits to actually
>> using.  I built the manual with Arsen's patches using 4.13a; the
>> build was successful, and I didn't see any obvious issues with the
>> @gol removal in either the PDF or HTML output, so I think we are OK
>> for backward compatibility.
> 
> FWIW macOS/Darwin (as delivered by Apple) is stuck on 4.8 (and,
> presumably, very unlikely to advance), but I would expect most macOS
> FOSS users have something newer installed, either self-built or via
> macposrts/homebrew etc. so the “admits to actually using” applies
> here too I think (personally, I am using 6.7 but not for any special
> reason other than it was current when I updated  my local toolset).
> So I think Darwin can also manage with a newer requirement.

Well, with 4.8 being too old to produce PDF output, that does kind of 
kill my idea of replacing the existing requirement for a specific 
Texinfo version with "the version that comes with your OS distribution 
is good enough".  :-(

AFAIK we have not knowingly changed any specific requirements beyond the 
stated 4.7 and 4.9 for PDF output, but it concerns me that nobody is 
likely to be using versions that old on a regular basis to make sure 
they continue to work and we haven't unknowingly introduced dependencies 
on newer Texinfo features.

Anyway, I think I will leave the existing requirement alone for now, and 
just add a note that newer versions produce better output.

-Sandra


  reply	other threads:[~2023-03-10 17:51 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 10:27 Arsen Arsenović
2023-02-23 10:27 ` [PATCH v2 1/5] docs: Create Indices appendix Arsen Arsenović
2023-03-09  3:16   ` Sandra Loosemore
2023-03-09 10:12     ` Arsen Arsenović
2023-03-09 20:38     ` Arsen Arsenović
2023-03-11  1:12       ` Sandra Loosemore
2023-03-11  1:34         ` Arsen Arsenović
2023-03-11 12:22         ` Arsen Arsenović
2023-03-11 19:22           ` Gerald Pfeifer
2023-03-11 20:22             ` Arsen Arsenović
2023-03-11 19:34           ` Sandra Loosemore
2023-03-11 20:14             ` Arsen Arsenović
2023-03-11 20:32               ` [PATCH v2] html: Set CONTENTS_OUTPUT_LOCATION=inline if makeinfo supports it Arsen Arsenović
2023-03-12 10:25               ` [PATCH v2 1/5] docs: Create Indices appendix Gerald Pfeifer
2023-03-12 12:23                 ` Arsen Arsenović
2023-02-23 10:27 ` [PATCH v2 2/5] **/*.texi: Reorder index entries Arsen Arsenović
2023-02-23 23:50   ` Gerald Pfeifer
2023-02-23 10:27 ` [PATCH v2 3/5] doc: Add @defbuiltin family of helpers, set documentlanguage Arsen Arsenović
2023-03-09 23:50   ` Sandra Loosemore
2023-02-23 10:27 ` [PATCH v2 4/5] Update texinfo.tex, remove the @gol macro/alias Arsen Arsenović
2023-03-09 23:55   ` Sandra Loosemore
2023-03-10  0:17     ` Gerald Pfeifer
2023-03-10 10:33       ` Thomas Schwinge
2023-03-10 12:49         ` Arsen Arsenović
2023-03-10 15:51           ` Gerald Pfeifer
2023-03-10 15:58             ` Arsen Arsenović
2023-03-10 12:48     ` Arsen Arsenović
2023-03-10 15:49     ` Arsen Arsenović
2023-03-18 20:14       ` Ping (gcc/configure.ac, docs): " Arsen Arsenović
2023-03-20 22:01         ` Sandra Loosemore
2023-03-20 23:06           ` Joseph Myers
2023-03-20 23:27             ` Arsen Arsenović
2023-03-20 23:35           ` Arsen Arsenović
2023-03-21  9:52             ` Arsen Arsenović
2023-03-21 23:11               ` Gerald Pfeifer
2023-02-23 10:27 ` [PATCH v2 5/5] update_web_docs_git: Update CSS reference to new manual CSS Arsen Arsenović
2023-03-10  0:07   ` Sandra Loosemore
2023-03-10 13:00     ` Arsen Arsenović
2023-02-25 22:04 ` [PATCH v2 0/5] A small Texinfo refinement Thomas Schwinge
2023-02-26 14:54   ` Arsen Arsenović
2023-03-08  1:56 ` Sandra Loosemore
2023-03-08  9:11   ` Arsen Arsenović
2023-03-08 18:38     ` Sandra Loosemore
2023-03-08 21:22       ` Arsen Arsenović
2023-03-09  1:09         ` Sandra Loosemore
2023-03-09  1:19           ` Andrew Pinski
2023-03-09  8:26             ` Richard Biener
2023-03-09 23:35               ` Sandra Loosemore
2023-03-10  8:50                 ` Iain Sandoe
2023-03-10 17:51                   ` Sandra Loosemore [this message]
2023-03-10 18:09                     ` Sandra Loosemore
2023-03-10 19:00                     ` Gerald Pfeifer
2023-03-13  9:05                       ` Richard Biener
2023-03-13 11:01                         ` Arsen Arsenović
2023-05-29 15:06                       ` NightStrike
2023-05-29 17:26                         ` Arsen Arsenović
2023-05-29 19:27                           ` Sandra Loosemore
2023-03-09 10:22           ` Arsen Arsenović
2023-03-09  8:28       ` Gerald Pfeifer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e45049c9-5042-13cd-ce0b-8bf0db8dca93@siemens.com \
    --to=sandra.loosemore@siemens.com \
    --cc=arsen@aarsen.me \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=idsandoe@googlemail.com \
    --cc=joseph@codesourcery.com \
    --cc=pinskia@gmail.com \
    --cc=richard.guenther@gmail.com \
    --cc=sandra@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).