public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: "Andrea Cervesato" <andrea.cervesato@suse.com>,
	ltp@lists.linux.it, "Ricardo B . Marlière" <rbm@suse.com>
Subject: Re: [LTP] [PATCH v4 2/5] doc: Add sphinx to requirements.txt
Date: Mon, 31 Mar 2025 18:37:26 +0200	[thread overview]
Message-ID: <20250331163726.GB220855@pevik> (raw)
In-Reply-To: <20250331163120.GA220855@pevik>

> > Hi Petr,

> > On 3/28/25 10:57, Petr Vorel wrote:
> > > Although that slightly prolongs creating virtualenv, it's probably
> > > better to handle it as the other requirements.

> > > Suggested-by: Andrea Cervesato <andrea.cervesato@suse.com>
> > > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > > ---
> > > New in v4.

> > >   doc/developers/documentation.rst | 2 --
> > >   doc/requirements.txt             | 1 +
> > >   2 files changed, 1 insertion(+), 2 deletions(-)

> > > diff --git a/doc/developers/documentation.rst b/doc/developers/documentation.rst
> > > index 27c847e125..a303253693 100644
> > > --- a/doc/developers/documentation.rst
> > > +++ b/doc/developers/documentation.rst
> > > @@ -23,8 +23,6 @@ Before building, make sure you have python3 ``virtualenv`` module installed.
> > >       # prepare virtual environment
> > >       python3 -m virtualenv .venv
> > >       . .venv/bin/activate
> > > -
> > > -    pip install sphinx # usually packaged in distros
> > >       pip install -r requirements.txt
> > >       # build documentation
> > > diff --git a/doc/requirements.txt b/doc/requirements.txt
> > > index 742fb8b4bb..1f4cefb2c6 100644
> > > --- a/doc/requirements.txt
> > > +++ b/doc/requirements.txt
> > > @@ -1,3 +1,4 @@
> > > +sphinx
> > In requirements.txt we usually put the right version of the package that we
> > want to use. We can use the latest, what do you think?

> I hesitated a bit if fixed versions are the best as sooner or later will have to
> be manually updated when it breaks, but sure - we use it anyway for other modules

> -sphinx
> -sphinx-rtd-theme==2.0.0
> +sphinx==8.2.3
> +sphinx-rtd-theme==3.0.2

> In that case I would remove python3-sphinx from apt install command in
> .github/workflows/ci-sphinx-doc.yml to match the command => I'll send v5
> of this change only.

Wait, one thing: we use doc/requirements.txt in .readthedocs.yml. Is it really a
good idea to add there sphinx, when it uses containers? I can test it in a
separate branch, but we discussed some time ago that we should avoid adding
sphinx for readthedocs.

Wouldn't be in the end better to keep 'pip install sphinx' in Makefile instead
(the previous proposal).

Kind regards,
Petr

> Kind regards,
> Petr

> > >   sphinx-rtd-theme==2.0.0
> > >   linuxdoc==20231020
> > >   sphinxcontrib-spelling==7.7.0
> > Andrea

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-03-31 16:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  9:57 [LTP] [PATCH v4 0/5] Update doc related Makefile Petr Vorel
2025-03-28  9:57 ` [LTP] [PATCH v4 1/5] doc/Makefile: Remove also metadata/ltp.json Petr Vorel
2025-03-28  9:57 ` [LTP] [PATCH v4 2/5] doc: Add sphinx to requirements.txt Petr Vorel
2025-03-28 13:02   ` Andrea Cervesato via ltp
2025-03-31 16:31     ` Petr Vorel
2025-03-31 16:37       ` Petr Vorel [this message]
2025-03-31 17:04         ` Andrea Cervesato via ltp
2025-03-31 17:53           ` Petr Vorel
2025-04-01  8:18             ` Andrea Cervesato via ltp
2025-04-01 12:17               ` Petr Vorel
2025-04-01 12:20                 ` Petr Vorel
2025-03-28  9:57 ` [LTP] [PATCH v4 3/5] doc/Makefile: Allow to create and use .venv Petr Vorel
2025-03-28 13:05   ` Andrea Cervesato via ltp
2025-03-28  9:57 ` [LTP] [PATCH v4 4/5] Makefile: Update 'doc' target, add 'doc-clean' Petr Vorel
2025-03-28 11:36   ` Ricardo B. Marli��re via ltp
2025-04-07 14:53     ` Petr Vorel
2025-04-08 19:11       ` Ricardo B. Marli��re via ltp
2025-04-09  8:12         ` Petr Vorel
2025-04-09 12:22           ` Ricardo B. Marli��re via ltp
2025-04-09 13:22             ` Petr Vorel
2025-03-28  9:57 ` [LTP] [PATCH v4 5/5] doc: Note 'make doc' in the building doc Petr Vorel
2025-03-28 13:18 ` [LTP] [PATCH v4 0/5] Update doc related Makefile Andrea Cervesato via ltp

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=20250331163726.GB220855@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --cc=ltp@lists.linux.it \
    --cc=rbm@suse.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