public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/sphinx-pre-install: add minimum support for RHEL
Date: Tue, 8 Aug 2017 05:55:14 -0300	[thread overview]
Message-ID: <20170808055514.28fc2057@vento.lan> (raw)
In-Reply-To: <20170807142733.6642b226@lwn.net>

Em Mon, 7 Aug 2017 14:27:33 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> On Mon, 24 Jul 2017 09:09:24 -0300
> Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
> 
> > RHEL 7.x and clone distros are shipped with Sphinx 1.1.x,
> > with is incompatible with Kernel ReST markups.
> > 
> > So, on those systems, the only alternative is to install
> > it via a Python virtual environment.
> > 
> > While seeking for "pip" on CentOS 7.3, I noticed that it
> > is not really needed, as python-virtualenv has its version
> > packaged there already. So, remove this from the list of
> > requirements for all distributions.
> > 
> > With regards to PDF, twe need at least texlive-tabulary
> > extension, but that is not shipped there (at least on
> > CentOS). So, disable PDF packages as a hole.
> > 
> > Please notice, however, that texlive + amsmath is needed for
> > ReST to properly handle ReST ".. math::" tags. Yet, Sphinx
> > fall back to display the LaTeX math expressions as-is, if
> > such extension is not available.
> > 
> > So, let's just disable all texlive packages as a hole.  
> 
> I've applied this, finally.  Couldn't resist the temptation to fix "as a
> whole" while I was at it :)

Thanks for applying - and for fixing the "whole" typo ;)

Yeah, RHEL/CentOS was likely the big missing gap at the script. With time,
people may end adding other distros there too. As most distros either
use .deb or .rpm packaging[1], I suspect it shouldn't be hard to add support
for them when needed, as they'll end by either use the existing logic,
or require a close enough logic.

[1] Well, last time I checked, Slackware still use tarballs. Slackware
was the first distro I used, back on Kernel 1.0 days. If I ever become 
nostalgic enough, I might eventually write a patch for it some day.

Thanks,
Mauro

      reply	other threads:[~2017-08-08  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 12:09 [PATCH] scripts/sphinx-pre-install: add minimum support for RHEL Mauro Carvalho Chehab
2017-08-07 20:27 ` Jonathan Corbet
2017-08-08  8:55   ` Mauro Carvalho Chehab [this message]

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=20170808055514.28fc2057@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.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