public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Florian Schmaus" <flow@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-tex/minted/
Date: Wed, 11 Dec 2024 08:49:17 +0000 (UTC)	[thread overview]
Message-ID: <1733906935.10dc5dfe7fd75ccaa15722c6509142cb0b8d916c.flow@gentoo> (raw)

commit:     10dc5dfe7fd75ccaa15722c6509142cb0b8d916c
Author:     Florian Schmaus <flow <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 11 08:43:10 2024 +0000
Commit:     Florian Schmaus <flow <AT> gentoo <DOT> org>
CommitDate: Wed Dec 11 08:48:55 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=10dc5dfe

dev-tex/minted: build documentation with just build latexminted

Based on a patch from Paul "negril" Zander. This allows us to drop the
circular BDEPEND on minted if USE=doc.

Signed-off-by: Florian Schmaus <flow <AT> gentoo.org>

 dev-tex/minted/minted-3.4.0.ebuild | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/dev-tex/minted/minted-3.4.0.ebuild b/dev-tex/minted/minted-3.4.0.ebuild
index 1acb9a3c9542..95f392722a0b 100644
--- a/dev-tex/minted/minted-3.4.0.ebuild
+++ b/dev-tex/minted/minted-3.4.0.ebuild
@@ -33,7 +33,6 @@ RDEPEND="
 "
 BDEPEND="
 	doc? (
-		>=dev-tex/minted-${PV}
 		dev-texlive/texlive-fontsextra
 	)
 "
@@ -74,8 +73,16 @@ src_install() {
 
 	pushd latex/minted &> /dev/null || die
 	local -x LATEX_DOC_ARGUMENTS="-shell-escape"
-	latex-package_src_install
+	latex-package_src_doinstall styles fonts bin
 	if use doc; then
+		python_setup
+		local -x PYTHONPATH="${ED}/usr/lib/${EPYTHON}/site-packages"
+		local -x PATH="${ED}/usr/lib/python-exec/${EPYTHON}:${PATH}"
+		latex-package_src_doinstall doc
+		# The following line shouldn't be required, as 'doc' is expaned
+		# by latex-package.eclass to "… dtx … pdf", but without this,
+		# the pdf is *not* installed. Maybe a bug in
+		# latex-package.eclass?
 		latex-package_src_doinstall pdf
 	fi
 	popd &> /dev/null || die


             reply	other threads:[~2024-12-11  8:49 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  8:49 Florian Schmaus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-27 18:36 [gentoo-commits] repo/gentoo:master commit in: dev-tex/minted/ Arthur Zamarin
2025-02-07 14:48 Arthur Zamarin
2025-02-07 14:44 Arthur Zamarin
2024-12-12 17:03 Florian Schmaus
2024-12-11  8:49 Florian Schmaus
2024-12-10 14:58 Florian Schmaus
2024-12-09 10:26 Florian Schmaus
2024-07-11  2:40 Ionen Wolkens
2024-06-21 15:47 Florian Schmaus
2024-06-21 15:47 Florian Schmaus
2024-06-21  4:23 Arthur Zamarin
2024-06-20 15:07 Ionen Wolkens
2024-06-14 17:29 Sam James
2024-06-14 17:29 Sam James
2024-06-14 17:20 Sam James
2024-06-14 17:20 Sam James
2024-06-14 14:42 Arthur Zamarin
2024-05-28 18:23 Arthur Zamarin
2024-05-26  6:06 Arthur Zamarin
2024-02-12 13:46 Jakov Smolić
2024-02-11 12:03 Sam James
2024-02-11 12:03 Sam James
2024-02-11 10:54 Florian Schmaus
2024-01-06  9:02 Sam James
2022-12-20 10:08 Maciej Barć
2022-12-19 22:28 Maciej Barć
2017-05-25 21:15 Patrice Clement
2017-05-25 21:12 Patrice Clement
2016-12-26 21:22 Kacper Kowalik
2016-03-11 16:17 Patrice Clement
2015-12-03 12:49 Justin Lecher
2015-12-03 10:21 Justin Lecher
2015-12-03 10:11 Guilherme Amadio
2015-12-03 10:11 Guilherme Amadio

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=1733906935.10dc5dfe7fd75ccaa15722c6509142cb0b8d916c.flow@gentoo \
    --to=flow@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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