From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] contrib: use sphinx-build from a venv
Date: Tue, 26 Jul 2022 13:01:44 +0100 [thread overview]
Message-ID: <CAH6eHdTWuHs+rMVAhJ5R9C7-jsA99tUzmXRKwvAmn82Yi_Kqsw@mail.gmail.com> (raw)
In-Reply-To: <Yt/WgIlDihiOC3yi@elastic.org>
On Tue, 26 Jul 2022 at 12:56, Frank Ch. Eigler wrote:
>
> Hi -
>
> > > The gccadmin team can do this kind of thing without overseer/root
> > > privileges, or indeed so can any local shell-privileged user.
> >
> > Yeah, I said I didn't want to install it that way without overseer
> > approval, as pip won't keep the packages up to date the way dnf
> > installations do.
>
> Indeed, but that's your own preference/responsibility and does not
> affect the system, so no overseer oversight is necessary.
OK, I can install it for Martin then.
> > > (That said, rhel8 includes sphynx 1.7.6 - are you sure that's
> > > not satisfactory?)
> >
> > That's a different package (full text search engine), what's needed
> > here is python3-sphinx.
>
> # rpm -q python3-sphinx
> python3-sphinx-1.7.6-2.el8.noarch
Oh right, yes, sorry, I got confused after I looked into the packages
myself. The "other sphinx" is in EPEL 8 as sphinx-2.2.11-15.el8
next prev parent reply other threads:[~2022-07-26 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7e41c1dd-d95a-0769-bfb5-c3713da240ab@suse.cz>
2022-07-26 7:26 ` Martin Liška
2022-07-26 11:45 ` Frank Ch. Eigler
2022-07-26 11:54 ` Jonathan Wakely
2022-07-26 11:56 ` Frank Ch. Eigler
2022-07-26 12:01 ` Jonathan Wakely [this message]
2022-07-26 12:17 ` 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=CAH6eHdTWuHs+rMVAhJ5R9C7-jsA99tUzmXRKwvAmn82Yi_Kqsw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=gcc-patches@gcc.gnu.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).