From: Mark Wielaard <mark@klomp.org>
To: Gerald Pfeifer via Overseers <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
"Gerald Pfeifer" <gerald@pfeifer.com>,
"Arsen Arsenović" <arsen@aarsen.me>
Subject: Re: Please update Texinfo on gcc.gnu.org
Date: Wed, 22 Mar 2023 01:17:43 +0100 [thread overview]
Message-ID: <20230322001743.GY24234@gnu.wildebeest.org> (raw)
In-Reply-To: <0b0d7974-fda0-ea5f-ac11-95ae43faa32e@pfeifer.com>
Hi Gerald,
On Wed, Mar 22, 2023 at 12:02:33AM +0100, Gerald Pfeifer via Overseers wrote:
> On Tue, 21 Mar 2023, Frank Ch. Eigler wrote:
> >> I'd like to request that the server building GCC texinfo-based
> >> documentation (which is, AFAIK, gcc.gnu.org) be updated to Texinfo
> >> master, currently at commit f12de7a5b383bed0ea29ee34c427679e0f8b9658.
> >> [...]
> >> Please let me know if there's anything extra that I should do.
> > Have you considered getting the shared gccadmin account to build &
> > install its private copy of texinfo under its home directory?
>
> I'm not sure how broadly we want to provide access to the gccadmin
> account, software supply chain and such? (In general, not particular
> to Arsen at all!)
I would keep it to just the people you trust. But I do think we can
trust Arsen and it would be good as a penance to make him part of
gccadmins so he can be responsible for keeping texinfo up to date :)
But what we really should do is setup a dedicated/isolated
vm/container to do snapshot and doc builds. And then let the buildbot
do them against the lowest and latest supported textinfo versions (or
at least against some supported distro versions).
> I'll try to have a look at installing an updated version of Texinfo
> and how to use it for our daily doc builds this coming weekend...
I already build a version and installed it under
/home/gccadmin/texinfo/install-git/
But I haven't tried to use it yet.
> (Not a big fan of using "random" Git versions in production, though;
> any chance for a regular release coming soon?)
Agreed. Building from git is also a bit of a pain since it needs a
newer automake and help2man.
Cheers,
Mark
next prev parent reply other threads:[~2023-03-22 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 11:11 Arsen Arsenović
2023-03-21 13:28 ` Frank Ch. Eigler
2023-03-21 15:24 ` Arsen Arsenović
2023-03-21 23:02 ` Gerald Pfeifer
2023-03-22 0:17 ` Mark Wielaard [this message]
2023-03-22 10:39 ` Arsen Arsenović
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=20230322001743.GY24234@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=arsen@aarsen.me \
--cc=fche@elastic.org \
--cc=gerald@pfeifer.com \
--cc=overseers@sourceware.org \
/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).