Please update Texinfo on gcc.gnu.org

Please update Texinfo on gcc.gnu.org

[Arsen Arsenović]

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

Hi,

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.

Getting an in-dev Texinfo installed and updating
maintainer-scripts/update_web_docs_git to use it and the new CSS (which
is a change that is currently committed in git) should be the last step
in the process of getting the recent Texinfo changes out to GCC users.

I've, so far, asked for approval for installing newer Texinfo on #gcc on
OFTC, and got an ACK from richi, and also asked in the original patch
thread (but it was late, so there have been no responses yet):
https://inbox.sourceware.org/gcc-patches/86sfdz2dyv.fsf@aarsen.me/

Please let me know if there's anything extra that I should do.

Thanks in advance, have a lovely day.
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

Re: Please update Texinfo on gcc.gnu.org

[Frank Ch. Eigler]

Hi -

> 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?

- FChE

Re: Please update Texinfo on gcc.gnu.org

[Arsen Arsenović]

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]


"Frank Ch. Eigler" <fche@elastic.org> writes:

> Hi -
>
>> 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?

That would be okay too, by my opinion (if not better, since it localizes
changes).  I don't have the power to do that myself, though, and was
asked to write to overseers, hence my email.

Thanks, have a great day.

> - FChE


-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

Re: Please update Texinfo on gcc.gnu.org

[Gerald Pfeifer]

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'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...

(Not a big fan of using "random" Git versions in production, though;
any chance for a regular release coming soon?)

Gerald

Re: Please update Texinfo on gcc.gnu.org

[Mark Wielaard]

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

Re: Please update Texinfo on gcc.gnu.org

[Arsen Arsenović]

[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]


Gerald Pfeifer <gerald@pfeifer.com> writes:

> 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'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...
>
> (Not a big fan of using "random" Git versions in production, though;
> any chance for a regular release coming soon?)

I'm not sure, I think Gavin sees these changes as new features, hence
landing in the next minor release of Texinfo (7.1) or so.  I'm not sure
there's a well defined timeline for these releases.  If you wish, I can
ask about it.

Thanks for updating the builder script, by the way.  Applying the new
Texinfo version should be as simple as adding it to $PATH, FWIW.

If so desired, I wouldn't mind looking into how to make the buildbot
build the docs in order to reduce the amount of code running under
gccadmin.  Mark suggested we should build both for the lowest supported
and the fancy new Texinfo versions.  We could set up a pair of builders
that build the fancy new Texinfo version (perhaps by having a
specification of how to pull a given version, so that we could use a
hand-managed commit hash or a dist tarball once we have applicable
releases) as well as the lowest supported version (which changes rarely,
so we can just put it in the runner Docker images even), and then have
the fancy new one use an SSH key stored in a Buildbot secret to update
the docs directory via a dedicated user.  I use a similar strategy on
sr.ht to push to my server:

  https://git.sr.ht/~arsen/www/tree/master/item/.build.yml

Thanks again, have a lovely day.

> Gerald

PS: For some reason, I didn't get your email delivered, so I needed to
scrape it from inbox.s.o and mangle it into my maildir.  Did you get a
bounce notification?

-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]