ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Markus Heiser <markus.heiser@darmarit.de>,
	Jani Nikula <jani.nikula@intel.com>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>,
	ksummit@lists.linux.dev
Subject: Re: [Ksummit-discuss] [TECH TOPIC] What kernel documentation could be
Date: Tue, 28 Jun 2022 12:01:42 +0100	[thread overview]
Message-ID: <20220628120142.4fe254f7@sal.lan> (raw)
In-Reply-To: <CAMuHMdW_EkQ8pSgJjrZtBXXkitRv2Wq+fP4wCnPmyvaPQO-kxA@mail.gmail.com>

Em Tue, 28 Jun 2022 09:57:29 +0200
Geert Uytterhoeven <geert@linux-m68k.org> escreveu:

> Hi Mauro,
> 
> On Tue, Jun 28, 2022 at 9:43 AM Mauro Carvalho Chehab
> <mchehab@kernel.org> wrote:
> > Em Mon, 27 Jun 2022 09:27:54 -0600
> > Jonathan Corbet <corbet@lwn.net> escreveu:  
> > > Markus Heiser <markus.heiser@darmarit.de> writes:  
> > > > IMO It is unnecessary that the build-chain must run on all
> > > > platforms and with all distributions.
> > > >
> > > > Who observes the Sphinx-doc & docutils development since (>15)
> > > > years is aware that with various (old) Sphinx-doc & docutils
> > > > versions no stable results can be produced, not without
> > > > complicating the build-chain.  And this is exactly the situation
> > > > we are facing today.
> > > >
> > > > The build chain of documentation has nothing to do with kernel
> > > > development (at least in my opinion) and should be decoupled from it:
> > > > maintaining one defined build environment is enough work ... this
> > > > becomes especially clear if you (as Jani recommends) rely more on
> > > > sphinx-modules and widely used tools.  
> > >
> > > The counterargument to this is that we want as many developers as
> > > possible to be able to build the docs and contribute to them.  We can't
> > > complain that developers have broken the docs build if we don't do what
> > > we can to help them do the build themselves.  
> >
> > Agreed.
> >  
> > > One of our longstanding contributors is on Sphinx 1.8.5:
> > >
> > >   https://lwn.net/ml/linux-doc/4c403239-3c71-4ab9-2168-f7e9d77008b2%40infradead.org/  
> 
> Ubuntu 20.04 LTS also has 1.8.5.
> Looks like I'll get 4.3.2 after upgrading to 22.04 LTS (which is only
> about two months old).

Yeah, LTS distros are the main reason why the default recommendation is to
install Sphinx via virtualenv/venv.

With RHEL9, SUSE 15 SP4 (plus CenOS and openSUSE Leap versions of them),
plus Ubuntu 22.04, maybe we can change the default to recommend installing
it via distro-provided packages. Yet, Debian bulseye has 2.5.0. Only
bookworm, scheduled for mid 2023, will come with Sphinx > 2.

Regards,
Mauro




  reply	other threads:[~2022-06-28 11:01 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 20:57 [TECH TOPIC] What kernel documentation could be Jonathan Corbet
2022-06-17 20:57 ` [Ksummit-discuss] " Jonathan Corbet
2022-06-17 21:48 ` Laurent Pinchart
2022-06-17 21:48   ` Laurent Pinchart
2022-06-27 15:18   ` Jonathan Corbet
2022-06-18  8:24 ` Mauro Carvalho Chehab
2022-06-18  8:24   ` Mauro Carvalho Chehab
2022-06-18 11:03   ` Miguel Ojeda
2022-06-18 11:16     ` Mauro Carvalho Chehab
2022-06-18 11:16       ` Mauro Carvalho Chehab
2022-06-18 14:37       ` Miguel Ojeda
2022-06-23  9:18   ` Jani Nikula
2022-06-23  9:57     ` Mauro Carvalho Chehab
2022-06-23 10:30       ` Jani Nikula
2022-06-23 13:40       ` Jonathan Corbet
2022-06-24  7:33         ` Mauro Carvalho Chehab
2022-06-24 16:37           ` Markus Heiser
2022-06-27 15:27             ` Jonathan Corbet
2022-06-27 15:31               ` Christoph Hellwig
2022-06-28  7:43               ` Mauro Carvalho Chehab
2022-06-28  7:57                 ` Geert Uytterhoeven
2022-06-28 11:01                   ` Mauro Carvalho Chehab [this message]
2022-07-02 12:43                     ` Stephen Rothwell
2022-06-24 22:57           ` Jonathan Corbet
2022-06-25  9:10             ` Mauro Carvalho Chehab
2022-06-25 14:00               ` Jonathan Corbet
2022-06-25 18:11                 ` Linus Torvalds
2022-06-26  7:55                   ` Mauro Carvalho Chehab
2022-06-26  9:26                     ` Mauro Carvalho Chehab
2022-06-26  9:53                     ` Mauro Carvalho Chehab
2022-06-27 15:28                       ` Liam Howlett
2022-06-27 15:54                         ` Christian Brauner
2022-06-27 16:27                         ` Mark Brown
2022-06-28 10:53                           ` Mauro Carvalho Chehab
2022-06-28 16:13                         ` Luck, Tony
2022-06-27 15:34                   ` Jonathan Corbet
2022-06-27 17:07                     ` Linus Torvalds
2022-07-02 10:52                   ` Mauro Carvalho Chehab
2022-06-25 17:43 ` Steven Rostedt
2022-06-25 17:48   ` Laurent Pinchart

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=20220628120142.4fe254f7@sal.lan \
    --to=mchehab@kernel.org \
    --cc=corbet@lwn.net \
    --cc=geert@linux-m68k.org \
    --cc=jani.nikula@intel.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=ksummit@lists.linux.dev \
    --cc=markus.heiser@darmarit.de \
    /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 NNTP newsgroup(s).