public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "John Helmert III" <ajak@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/rizin/
Date: Sat, 01 Feb 2025 23:08:51 +0000 (UTC)	[thread overview]
Message-ID: <1738451303.869e31e5d7fc025c7de569bbda124f0b9d817d4a.ajak@gentoo> (raw)

commit:     869e31e5d7fc025c7de569bbda124f0b9d817d4a
Author:     John Helmert III <ajak <AT> gentoo <DOT> org>
AuthorDate: Sat Feb  1 23:08:23 2025 +0000
Commit:     John Helmert III <ajak <AT> gentoo <DOT> org>
CommitDate: Sat Feb  1 23:08:23 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=869e31e5

dev-util/rizin: drop 0.7.3-r1

Bug: https://bugs.gentoo.org/949208
Signed-off-by: John Helmert III <ajak <AT> gentoo.org>

 dev-util/rizin/rizin-0.7.3-r1.ebuild | 103 -----------------------------------
 1 file changed, 103 deletions(-)

diff --git a/dev-util/rizin/rizin-0.7.3-r1.ebuild b/dev-util/rizin/rizin-0.7.3-r1.ebuild
deleted file mode 100644
index ecc511746011..000000000000
--- a/dev-util/rizin/rizin-0.7.3-r1.ebuild
+++ /dev/null
@@ -1,103 +0,0 @@
-# Copyright 1999-2024 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-PYTHON_COMPAT=( python3_{10..13} )
-
-# This is the commit that the CI for the release commit used
-BINS_COMMIT="1203a9a2f51e32337c8434d9f4f7c4543552e271"
-
-inherit flag-o-matic meson python-any-r1
-
-DESCRIPTION="reverse engineering framework for binary analysis"
-HOMEPAGE="https://rizin.re/"
-
-SRC_URI="mirror+https://github.com/rizinorg/rizin/releases/download/v${PV}/rizin-src-v${PV}.tar.xz
-	test? ( https://github.com/rizinorg/rizin-testbins/archive/${BINS_COMMIT}.tar.gz -> rizin-testbins-${BINS_COMMIT}.tar.gz )"
-S="${WORKDIR}/${PN}-v${PV}"
-
-LICENSE="Apache-2.0 BSD LGPL-3 MIT"
-SLOT="0/${PV}"
-KEYWORDS="amd64 ~arm64 ~x86"
-IUSE="test"
-
-# Need to audit licenses of the binaries used for testing
-RESTRICT="test? ( fetch ) !test? ( test )"
-
-# TODO: unbundle dev-libs/blake3
-RDEPEND="
-	app-arch/lz4:0=
-	app-arch/xz-utils
-	app-arch/zstd:=
-	>=dev-libs/capstone-5:0=
-	dev-libs/libmspack
-	dev-libs/libzip:0=
-	dev-libs/openssl:0=
-	dev-libs/libpcre2:0=
-	>=dev-libs/tree-sitter-0.19.0:=
-	dev-libs/tree-sitter-c
-	dev-libs/xxhash
-	sys-apps/file
-	sys-libs/zlib:0=
-"
-DEPEND="${RDEPEND}"
-BDEPEND="${PYTHON_DEPS}"
-
-PATCHES=(
-	"${FILESDIR}/${PN}-0.4.0-never-rebuild-parser.patch"
-)
-
-src_prepare() {
-	default
-
-	local py_to_mangle=(
-		librz/core/cmd_descs/cmd_descs_generate.py
-		sys/clang-format.py
-		test/fuzz/scripts/fuzz_rz_asm.py
-		test/scripts/gdbserver.py
-	)
-
-	python_fix_shebang "${py_to_mangle[@]}"
-
-	# https://github.com/rizinorg/rizin/issues/3459
-	sed -ie '/dyld_chained_ptr_arm64e_auth/d' test/unit/test_bin_mach0.c || die
-
-	if use test; then
-		cp -r "${WORKDIR}/rizin-testbins-${BINS_COMMIT}" "${S}/test/bins" || die
-		cp -r "${WORKDIR}/rizin-testbins-${BINS_COMMIT}" "${S}" || die
-	fi
-}
-
-src_configure() {
-	# workaround tree-sitter-c induced underlinking in bug 928301
-	append-ldflags -ltree-sitter
-
-	local emesonargs=(
-		-Dcli=enabled
-		-Duse_sys_capstone=enabled
-		-Duse_sys_libmspack=enabled
-		-Duse_sys_libzip=enabled
-		-Duse_sys_libzstd=enabled
-		-Duse_sys_lz4=enabled
-		-Duse_sys_lzma=enabled
-		-Duse_sys_magic=enabled
-		-Duse_sys_openssl=enabled
-		-Duse_sys_pcre2=enabled
-		-Duse_sys_tree_sitter=enabled
-		-Duse_sys_xxhash=enabled
-		-Duse_sys_zlib=enabled
-
-		$(meson_use test enable_tests)
-		$(meson_use test enable_rz_test)
-	)
-	meson_src_configure
-}
-
-src_test() {
-	# We can select running either unit or integration tests, or all of
-	# them by not passing --suite. According to upstream, integration
-	# tests are more fragile and unit tests are sufficient for testing
-	# packaging, so only run those.
-	meson_src_test --suite unit
-}


             reply	other threads:[~2025-02-01 23:08 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-01 23:08 John Helmert III [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-09  2:54 [gentoo-commits] repo/gentoo:master commit in: dev-util/rizin/ John Helmert III
2025-02-01 23:08 John Helmert III
2025-02-01 23:08 John Helmert III
2025-01-20 23:56 John Helmert III
2024-12-15  4:57 John Helmert III
2024-09-02  6:00 John Helmert III
2024-07-28 18:51 John Helmert III
2024-07-28 18:51 John Helmert III
2024-07-28  2:39 Sam James
2024-05-11 19:08 Sam James
2024-04-21 23:33 John Helmert III
2024-04-21 23:33 John Helmert III
2024-04-15  7:25 Matthew Smith
2024-03-04  5:21 John Helmert III
2024-03-04  5:21 John Helmert III
2023-12-15  7:36 Sam James
2023-10-25 18:19 John Helmert III
2023-09-25  4:49 John Helmert III
2023-09-25  4:49 John Helmert III
2023-09-17  0:06 John Helmert III
2023-09-10 18:04 John Helmert III
2023-09-10 18:04 John Helmert III
2023-09-10 18:04 John Helmert III
2023-08-31  4:21 Sam James
2023-08-31  4:21 Sam James
2023-04-30 23:36 John Helmert III
2023-04-30 23:36 John Helmert III
2023-04-19  6:07 Sam James
2023-04-16 18:52 John Helmert III
2023-02-19 16:46 John Helmert III
2023-02-19  0:58 John Helmert III
2022-10-29 21:32 Sam James
2022-09-10 15:29 John Helmert III
2022-09-09 17:24 John Helmert III
2022-09-09 17:24 John Helmert III
2022-07-04 20:01 John Helmert III
2022-07-04 20:01 John Helmert III
2022-05-11  2:11 Sam James
2022-03-02  2:43 John Helmert III
2022-01-10  6:10 John Helmert III
2022-01-09  7:39 John Helmert III
2021-11-20 23:30 John Helmert III
2021-11-20 17:26 John Helmert III
2021-09-09  4:22 Sam James
2021-07-02  5:58 Sergei Trofimovich
2021-06-10 17:51 Sergei Trofimovich
2021-05-15 13:58 Sergei Trofimovich
2021-05-01 20:44 Sergei Trofimovich
2021-04-24 23:11 Sergei Trofimovich
2021-04-24 12:37 Sergei Trofimovich
2021-04-09  9:58 Sergei Trofimovich
2021-04-09  9:52 Sergei Trofimovich
2021-04-08 20:57 John Helmert III
2021-04-06 19:03 Sergei Trofimovich
2021-04-02  9:54 Sergei Trofimovich
2021-03-31 15:42 John Helmert III
2021-03-29 19:35 Sergei Trofimovich

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=1738451303.869e31e5d7fc025c7de569bbda124f0b9d817d4a.ajak@gentoo \
    --to=ajak@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