From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH] sphinx-pre-install: check for the need of graphviz-gd
Date: Mon, 17 Jul 2017 08:38:41 -0300 [thread overview]
Message-ID: <1d91c9bee26467b7b41bcba72eef9ca2540f96e1.1500291424.git.mchehab@s-opensource.com> (raw)
On newer versions of graphviz, it is needed to install a separate
package for PDF support.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
---
This patch depends on a previous patch series I sent yesterday. This,
together with the other pending patches are available at:
https://git.linuxtv.org/mchehab/experimental.git/log/?h=sphinx_install_v2
scripts/sphinx-pre-install | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/scripts/sphinx-pre-install b/scripts/sphinx-pre-install
index 230d9cc7ee1d..817241c674d3 100755
--- a/scripts/sphinx-pre-install
+++ b/scripts/sphinx-pre-install
@@ -285,6 +285,10 @@ sub give_redhat_hints()
"xelatex" => "texlive-xetex-bin",
);
+ my @fedora26_opt_pkgs = (
+ "graphviz-gd", # Fedora 26: needed for PDF support
+ );
+
my @fedora_tex_pkgs = (
"texlive-collection-fontsrecommended",
"texlive-collection-latex",
@@ -293,6 +297,11 @@ sub give_redhat_hints()
"dejavu-sans-mono-fonts",
);
+ my $release;
+
+ $release = $1 if ($system_release =~ /Fedora\s+release\s+(\d+)/);
+
+ check_rpm_missing(\@fedora26_opt_pkgs, 1) if ($pdf && $release >= 26);
check_rpm_missing(\@fedora_tex_pkgs, 1) if ($pdf);
check_missing_tex(1) if ($pdf);
check_missing(\%map);
--
2.13.3
reply other threads:[~2017-07-17 11:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1d91c9bee26467b7b41bcba72eef9ca2540f96e1.1500291424.git.mchehab@s-opensource.com \
--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
all inboxes | Powered by JetHome®