From: "Matthias Schwarzott" <zzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/pahole/
Date: Mon, 24 Jun 2024 13:06:15 +0000 (UTC) [thread overview]
Message-ID: <1719234304.9dc7afb8b8e60d94e57897399cedbf590f399c0e.zzam@gentoo> (raw)
commit: 9dc7afb8b8e60d94e57897399cedbf590f399c0e
Author: Matthias Schwarzott <zzam <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 24 13:05:04 2024 +0000
Commit: Matthias Schwarzott <zzam <AT> gentoo <DOT> org>
CommitDate: Mon Jun 24 13:05:04 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9dc7afb8
dev-util/pahole: add 1.27
Signed-off-by: Matthias Schwarzott <zzam <AT> gentoo.org>
dev-util/pahole/Manifest | 2 +
dev-util/pahole/pahole-1.27.ebuild | 78 ++++++++++++++++++++++++++++++++++++++
2 files changed, 80 insertions(+)
diff --git a/dev-util/pahole/Manifest b/dev-util/pahole/Manifest
index 768a7b64de02..34d4bcd44086 100644
--- a/dev-util/pahole/Manifest
+++ b/dev-util/pahole/Manifest
@@ -2,4 +2,6 @@ DIST dwarves-1.24.tar.xz 875744 BLAKE2B 6766b5a5ecbf64013227e7cd459af662fc213f23
DIST dwarves-1.25.tar.xz 2244876 BLAKE2B 1926fa1fa123fc3ad0f7f063406260b1e1e2611c563fedebee4c837e491164571fdb40408421c0c4ea2fd24e89c54a7a1ea669313b6dd6d7dcfa4934e2c1336e SHA512 104bfb8712d863e04d0c827c008b23ebc49543b17bfb5b44ce276a5b3d39f12cf71f721055ae2e5f430aa77a3c70f85f6eeaf72fd8c1cdf547260488bc5b5070
DIST dwarves-1.26.tar.sign 228 BLAKE2B 211f73da11d6ed61383fc0470c298360e7acae5fbeb2f963533fd3a984257f35b5626f04de9de92326723f06bea95a38903cee7f602146b12b1333cea2b720d0 SHA512 2f92951019847cddbfe90cd0e49a5746ca4886e25a9f8e26697688bec25d667255556bdc1ab897021eaa739d067a8d3e4fbbd0d7c9f7f56934676616fa11bce8
DIST dwarves-1.26.tar.xz 2250036 BLAKE2B cb86bf964f22633432e80d335937379c2096877c6130f49dbe03f2653b7c932bb1c5d87621ac93383be9e4f35294a4f95aadb6392491fb782812db519b39b666 SHA512 72e3c708ac6304d28daaab1c4365b66252d016987cbf33ec6d18456718478d7b96d6916dc3686069a386e97a9db355bb1e5e078c0c7b40e93bd7e8bd0b0380be
+DIST dwarves-1.27.tar.sign 228 BLAKE2B c15de74840aac809912b4b8bdd4c9171ba909bf6ad5d1466b33e67371455c19182e713d1a6abe134205cef909be5a5c1dcf8a24964b9e17fe1903963e7682e20 SHA512 4f46766f4d0bdd2d6b5409a62d59eb4f27473bd78aa2a9e03b44f13f740dab94e41ce565a44428f042f1b9eaf465392c136398aebc532b339db2a6d0b147fdfa
+DIST dwarves-1.27.tar.xz 2254968 BLAKE2B 0a0f8ec8bf26240e17dc3319e76e16299514d662a79b25c4c962f723127f55d185d557adba7230d23b2e2b38fc62044aaa3474a458dc3df2000260637f995121 SHA512 4eae00e2e5b636fce6c6b38f59ac561b0e613c23af1bc6e16d9e9df2b71323e090d4101dde7e5020e30c2251c364cb731c82865fd0c65c4aa417b7cc706cfe25
DIST pahole-1.24_p20221024-patches.tar.xz 22088 BLAKE2B b39458400411dd7da0f568257f42164952e170b952e4893a92d769e17ce4cf0de88b727808a38195438fe10e5537f245bf101f647f383b6df7642c5446fa5d45 SHA512 93f160f01023c5402535a34d59005f0a3e056662a2764722480d71b6e522f3bfef0d642084467d1fbea96e23386b4cbb708243713d59eb84f4f767c1ac5ab3f5
diff --git a/dev-util/pahole/pahole-1.27.ebuild b/dev-util/pahole/pahole-1.27.ebuild
new file mode 100644
index 000000000000..37c3f429d6d8
--- /dev/null
+++ b/dev-util/pahole/pahole-1.27.ebuild
@@ -0,0 +1,78 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+PYTHON_COMPAT=( python3_{9..12} )
+inherit cmake python-single-r1
+
+MY_PN=dwarves
+MY_P=${MY_PN}-${PV%%_p*}
+
+DESCRIPTION="pahole (Poke-a-Hole) and other DWARF utilities"
+HOMEPAGE="https://git.kernel.org/cgit/devel/pahole/pahole.git/"
+
+if [[ ${PV} == 9999 ]] ; then
+ EGIT_REPO_URI="https://git.kernel.org/pub/scm/devel/pahole/pahole.git"
+ inherit git-r3
+else
+ VERIFY_SIG_OPENPGP_KEY_PATH=/usr/share/openpgp-keys/arnaldocarvalhodemelo.asc
+ inherit verify-sig
+ SRC_URI="http://fedorapeople.org/~acme/${MY_PN}/${MY_P}.tar.xz
+ verify-sig? ( http://fedorapeople.org/~acme/${MY_PN}/${MY_P}.tar.sign )"
+ if [[ ${PV} == *_p* ]] ; then
+ # Patch rollups from git format-patch. Sometimes there are important
+ # fixes in git which haven't been released (and no release in sight).
+ # Patch rollups are a bit better for understanding where changes have
+ # come from for users.
+ SRC_URI+=" https://dev.gentoo.org/~sam/distfiles/${CATEGORY}/${PN}/${P}-patches.tar.xz"
+ fi
+ S="${WORKDIR}"/${MY_P}
+ BDEPEND="verify-sig? ( sec-keys/openpgp-keys-arnaldocarvalhodemelo )"
+ KEYWORDS="~amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~x86"
+fi
+
+LICENSE="GPL-2" # only
+SLOT="0"
+IUSE="debug"
+REQUIRED_USE="${PYTHON_REQUIRED_USE}"
+
+RDEPEND="${PYTHON_DEPS}
+ >=dev-libs/elfutils-0.178
+ sys-libs/zlib"
+DEPEND="${RDEPEND}"
+
+DOCS=( README README.ctracer NEWS )
+
+PATCHES=(
+ "${FILESDIR}"/${PN}-1.10-python-import.patch
+)
+
+src_unpack() {
+ if [[ ${PV} == 9999 ]] ; then
+ git-r3_src_unpack
+ return
+ fi
+
+ # Upstream sign the decompressed .tar
+ if use verify-sig; then
+ einfo "Unpacking ${MY_P}.tar.xz ..."
+ verify-sig_verify_detached - "${DISTDIR}"/${MY_P}.tar.sign \
+ < <(xz -cd "${DISTDIR}"/${MY_P}.tar.xz | tee >(tar -x))
+ assert "Unpack failed"
+ else
+ default
+ fi
+}
+
+src_prepare() {
+ [[ -d "${WORKDIR}"/${P}-patches ]] && PATCHES+=( "${WORKDIR}"/${P}-patches )
+
+ cmake_src_prepare
+ python_fix_shebang ostra/ostra-cg ostra/python/ostra.py
+}
+
+src_configure() {
+ local mycmakeargs=( "-D__LIB=$(get_libdir)" )
+ cmake_src_configure
+}
next reply other threads:[~2024-06-24 13:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 13:06 Matthias Schwarzott [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-23 15:53 [gentoo-commits] repo/gentoo:master commit in: dev-util/pahole/ Matthias Schwarzott
2025-01-22 20:16 Matthias Schwarzott
2025-01-22 20:16 Matthias Schwarzott
2025-01-12 21:22 David Seifert
2024-10-04 7:58 Sam James
2024-09-05 17:59 Sam James
2024-09-05 14:32 Sam James
2024-09-05 14:30 Sam James
2024-09-05 14:30 Sam James
2024-09-05 12:35 Sam James
2024-09-05 12:33 Sam James
2024-09-05 12:33 Sam James
2024-08-25 10:18 Jakov Smolić
2024-08-25 10:18 Jakov Smolić
2024-08-25 10:18 Jakov Smolić
2024-08-25 10:18 Jakov Smolić
2024-08-25 9:51 Arthur Zamarin
2024-08-25 9:51 Arthur Zamarin
2024-06-22 5:50 Matthias Schwarzott
2024-06-20 10:31 Sam James
2024-06-05 6:32 Matthias Schwarzott
2024-05-28 13:54 Matthias Schwarzott
2024-03-13 4:48 Sam James
2024-03-10 23:21 Jakov Smolić
2024-03-10 20:00 Arthur Zamarin
2024-03-10 20:00 Arthur Zamarin
2024-03-10 19:52 Arthur Zamarin
2024-03-10 19:52 Arthur Zamarin
2024-02-28 20:10 Matthias Schwarzott
2023-07-16 14:23 Sam James
2023-07-16 14:23 Sam James
2023-07-16 14:23 Sam James
2023-07-16 14:23 Sam James
2023-07-16 14:20 Sam James
2023-07-11 11:03 WANG Xuerui
2023-06-30 4:37 Matthias Schwarzott
2023-04-15 7:17 Matthias Schwarzott
2023-03-22 18:45 Andreas Sturmlechner
2023-03-13 22:11 Sam James
2023-03-13 21:24 Sam James
2023-03-13 20:51 Sam James
2023-03-13 20:51 Sam James
2023-03-13 20:35 Arthur Zamarin
2023-01-19 2:49 Sam James
2022-09-05 7:35 Matthias Schwarzott
2022-06-05 2:32 Matt Turner
2022-05-22 0:54 Yixun Lan
2022-05-20 6:11 Matthias Schwarzott
2022-05-20 6:11 Matthias Schwarzott
2022-04-15 6:36 Arthur Zamarin
2022-04-13 23:01 Sam James
2022-03-12 16:26 Arthur Zamarin
2022-03-10 10:10 Jakov Smolić
2022-03-10 9:03 Jakov Smolić
2021-12-17 11:45 Matthias Schwarzott
2021-12-16 21:45 Georgy Yakovlev
2021-11-07 16:16 罗百科
2021-06-02 8:20 Matthias Schwarzott
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=1719234304.9dc7afb8b8e60d94e57897399cedbf590f399c0e.zzam@gentoo \
--to=zzam@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