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/pgf/
Date: Sat, 18 Jan 2025 11:56:50 +0000 (UTC)	[thread overview]
Message-ID: <1737201351.1d7e5f26a2b39773a3392555b16c47c0a95935e0.flow@gentoo> (raw)

commit:     1d7e5f26a2b39773a3392555b16c47c0a95935e0
Author:     Florian Schmaus <flow <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 18 11:54:29 2025 +0000
Commit:     Florian Schmaus <flow <AT> gentoo <DOT> org>
CommitDate: Sat Jan 18 11:55:51 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1d7e5f26

dev-tex/pgf: fix pgf.revision.tex

Upstream creates the pgf.revision.tex as part of its build.lua and the
l3build invocation. We previously used a wrong date for
pgf(re)visiondate and an outdated scheme of pgf.revision.tex.

Closes: https://bugs.gentoo.org/948233
Signed-off-by: Florian Schmaus <flow <AT> gentoo.org>

 dev-tex/pgf/pgf-3.1.10-r1.ebuild | 53 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 53 insertions(+)

diff --git a/dev-tex/pgf/pgf-3.1.10-r1.ebuild b/dev-tex/pgf/pgf-3.1.10-r1.ebuild
new file mode 100644
index 000000000000..f7fc6422fb61
--- /dev/null
+++ b/dev-tex/pgf/pgf-3.1.10-r1.ebuild
@@ -0,0 +1,53 @@
+# Copyright 1999-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit latex-package
+
+DESCRIPTION="The TeX Portable Graphic Format"
+HOMEPAGE="https://github.com/pgf-tikz/pgf"
+SRC_URI="
+	https://github.com/pgf-tikz/pgf/archive/${PV}.tar.gz -> ${P}.tar.gz
+	doc? ( https://github.com/pgf-tikz/pgf/releases/download/${PV}/pgfmanual-${PV}.pdf -> ${P}-pgfmanual.pdf )
+"
+
+LICENSE="GPL-2 LPPL-1.3c FDL-1.2"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+IUSE="doc source"
+
+RDEPEND="dev-texlive/texlive-latexrecommended"
+
+# ADJUST ON BUMPS: The date of the according release tag. See also
+# upstream's build.lua
+PGF_VERSION_DATE="2023-01-15"
+
+src_install() {
+	einstalldocs
+
+	insinto "${TEXMF}"
+	doins -r tex
+	insinto "${TEXMF}"/tex/generic/${PN}
+	newins - pgf.revision.tex <<EOF
+\\def\\pgfrevision{${PV}}
+\\def\\pgfversion{${PV}}
+\\def\\pgfrevisiondate{${PGF_VERSION_DATE}}
+\\def\\pgfversiondate{${PGF_VERSION_DATE}}
+EOF
+
+	if use source ; then
+		doins -r source
+	fi
+
+	if use doc; then
+		cd "${S}/doc/generic/pgf" || die
+		docinto texdoc
+		# pgfmanual is now split from the main tar archive
+		newdoc "${DISTDIR}/${P}-pgfmanual.pdf" pgfmanual.pdf
+		doins -r images
+
+		dosym "../../../doc/${PF}/texdoc" "${TEXMF}/doc/latex/${PN}"
+		docompress -x "/usr/share/doc/${P}/texdoc/"
+	fi
+}


             reply	other threads:[~2025-01-18 11:56 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-18 11:56 Florian Schmaus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-18 12:12 [gentoo-commits] repo/gentoo:master commit in: dev-tex/pgf/ Florian Schmaus
2025-01-18 12:12 Florian Schmaus
2024-06-20 21:46 Sam James
2024-06-14 17:36 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 17:20 Sam James
2024-06-14 14:42 Arthur Zamarin
2024-02-09 21:03 Florian Schmaus
2024-02-09 21:03 Florian Schmaus
2023-04-29  7:51 Arthur Zamarin
2023-03-24 13:29 Arthur Zamarin
2023-03-22 22:36 Sam James
2022-12-04  9:23 WANG Xuerui
2022-04-17 18:32 Sam James
2022-02-03 22:59 Matthias Maier
2021-07-15 10:28 Marek Szuba
2021-04-01 22:32 Sam James
2021-04-01 22:30 Sam James
2021-04-01 22:30 Sam James
2021-04-01 22:27 Sam James
2021-04-01 22:27 Sam James
2021-04-01 17:55 Sergei Trofimovich
2021-04-01 17:55 Sergei Trofimovich
2021-04-01 12:11 Thomas Deutschmann
2021-01-06 22:35 Fabian Groffen
2020-01-09 20:55 Mikle Kolyada
2020-01-08 16:16 Mikle Kolyada
2019-11-16 15:41 Mikle Kolyada
2019-11-04 14:57 Mikle Kolyada
2019-11-04 13:27 Mikle Kolyada
2019-10-06  6:03 Mikle Kolyada
2019-10-02 10:42 Mikle Kolyada
2019-09-29 10:31 Mikle Kolyada
2019-09-29 10:28 Mikle Kolyada
2019-09-29 10:23 Mikle Kolyada
2019-09-29 10:20 Mikle Kolyada
2019-09-27 19:33 Mikle Kolyada
2019-09-27 19:30 Mikle Kolyada
2019-09-27 19:27 Mikle Kolyada
2019-09-27 19:19 Mikle Kolyada
2019-08-18 18:20 Mikle Kolyada
2019-08-18 18:20 Mikle Kolyada
2019-08-18 17:59 Mikle Kolyada
2019-08-18 17:59 Mikle Kolyada
2019-08-07  9:01 Mikle Kolyada
2019-08-07  9:01 Mikle Kolyada
2019-08-07  8:54 Mikle Kolyada
2019-07-17 11:22 Mikle Kolyada
2019-07-17 11:22 Mikle Kolyada
2019-06-13 15:59 Mikle Kolyada
2019-06-13 15:59 Mikle Kolyada
2019-05-14 17:53 Aaron Bauman
2018-08-18  2:49 Mikle Kolyada
2018-03-21  6:48 Matt Turner
2017-06-24  9:12 Markus Meier
2017-06-21 11:57 Agostino Sarubbo
2017-06-20 14:56 Tobias Klausmann
2017-06-18 20:12 Sergei Trofimovich
2017-06-12 12:41 Agostino Sarubbo
2017-05-19  1:29 Michael Weber
2017-02-08 17:38 Alexis Ballier
2016-02-04 17:28 Tobias Klausmann
2016-02-01  8:26 Alexis Ballier
2015-11-21 15:42 Markus Meier
2015-11-18  9:32 Agostino Sarubbo
2015-11-12 10:51 Agostino Sarubbo
2015-11-11  9:54 Agostino Sarubbo
2015-11-10 11:45 Agostino Sarubbo
2015-08-15  9:12 Alexis Ballier

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=1737201351.1d7e5f26a2b39773a3392555b16c47c0a95935e0.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