From: "Martin Liška" <mliska@suse.cz>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>, "Frank Ch. Eigler" <fche@elastic.org>
Subject: Server package installation - Sphinx
Date: Tue, 8 Nov 2022 09:03:39 +0100 [thread overview]
Message-ID: <8a994638-ce56-f838-b8e7-4d3f01a316c6@suse.cz> (raw)
Hi.
Tomorrow, I'm planning migrating the GCC documentation to Sphinx and I would like
to prepare for switching of the server-side documentation generation. That's currently
done with maintainer-scripts/update_web_docs_git job that modifies HTML, PDF and other
files we can see here: https://gcc.gnu.org/onlinedocs/. That's something I'll work on tomorrow.
For now, I would need to update the existing env:
$ /home/gccadmin/venv/bin/pip --upgrade sphinx
and add Sphinx deps:
$ /home/gccadmin/venv/bin/pip install furo sphinx-copybutton
Apart from that, I will need Texlive-related packages:
python-sphinx-latex
texlive-xindy
Hope these will be available on a RHEL instance we have and pull required
LaTeX sub-packages.
Feel free to reach me out at IRC.
Thanks,
Martin
next reply other threads:[~2022-11-08 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 8:03 Martin Liška [this message]
2022-11-08 9:00 ` Frank Ch. Eigler
2022-11-08 11:19 ` Martin Liška
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=8a994638-ce56-f838-b8e7-4d3f01a316c6@suse.cz \
--to=mliska@suse.cz \
--cc=fche@elastic.org \
--cc=mark@klomp.org \
--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).