All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH RFC] scripts/sphinx-pre-install: add a script to check Sphinx install
Date: Sat, 15 Jul 2017 09:55:09 -0300	[thread overview]
Message-ID: <20170715095509.27503544@vento.lan> (raw)
In-Reply-To: <20170715094940.2bcd7eab@vento.lan>

Em Sat, 15 Jul 2017 09:49:40 -0300
Mauro Carvalho Chehab <mchehab@s-opensource.com> escreveu:

> I guess it could also use kpsewhich to check if the needed
> texlive packages are installed. However, the problem with such
> approach is that texlive-kpathsea-bin package should be installed
> first, in order to provide such command.
> 
> So, installing PDF and math dependencies would require two steps.

Hmm... answering myself: if texlive-kpathsea-bin is not installed,
that probably means that texlive is not installed. So, the script
can just give the command to install all texlive packages that are
needed for a given distribution.

Thanks,
Mauro

  reply	other threads:[~2017-07-15 12:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 16:49 [PATCH RFC] scripts/sphinx-pre-install: add a script to check Sphinx install Mauro Carvalho Chehab
2017-07-14 17:35 ` Markus Heiser
2017-07-14 22:51   ` Jim Davis
2017-07-15  1:27     ` Mauro Carvalho Chehab
2017-07-15  2:21   ` Mauro Carvalho Chehab
2017-07-15  9:51     ` Markus Heiser
2017-07-15 12:49       ` Mauro Carvalho Chehab
2017-07-15 12:55         ` Mauro Carvalho Chehab [this message]
2017-07-15 19:27           ` Mauro Carvalho Chehab
2017-07-16  7:29         ` Markus Heiser
2017-07-16  9:57           ` Mauro Carvalho Chehab

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=20170715095509.27503544@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.