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: Wed, 31 Mar 2021 15:42:58 +0000 (UTC)	[thread overview]
Message-ID: <1617205370.1216ea4d1ffae3bb3a94c31f4b513150eb86576d.ajak@gentoo> (raw)

commit:     1216ea4d1ffae3bb3a94c31f4b513150eb86576d
Author:     John Helmert III <ajak <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 31 15:42:06 2021 +0000
Commit:     John Helmert III <ajak <AT> gentoo <DOT> org>
CommitDate: Wed Mar 31 15:42:50 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1216ea4d

dev-util/rizin: add 0.1.2

Fix tests, use system tree-sitter.

Signed-off-by: John Helmert III <ajak <AT> gentoo.org>

 dev-util/rizin/Manifest           |  2 ++
 dev-util/rizin/rizin-0.1.2.ebuild | 60 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 62 insertions(+)

diff --git a/dev-util/rizin/Manifest b/dev-util/rizin/Manifest
index 97ccecd84fd..0f1272bae1b 100644
--- a/dev-util/rizin/Manifest
+++ b/dev-util/rizin/Manifest
@@ -1 +1,3 @@
 DIST rizin-src-0.1.1.tar.xz 5475164 BLAKE2B 7646f07d462f0c7e9874fe29bf0b638f0d10756c2189e2811ee1711c6feb9b76e5c5e90574c084c568a8fbe204c8867e6bfad17f12567fa4a579924bdbda6932 SHA512 da3842e2b8534d1440aed547cf7a7ee351527d78883e7f989509b50cd99d3aebabb9307169a9a5cfcf6d82a8cf5ade5c653d2fdbf6b7d2052e46f049b1a4d035
+DIST rizin-src-0.1.2.tar.xz 5559560 BLAKE2B a9182ae49782c57c3c4d4028203cfb1aef5b743096f4749a0ba65fa80ee421a23c3eb8a4f413f06f51c909c763a9bb06cb058cd334b3f4b0711ff72ee93c0df6 SHA512 f52987af5d1cd9f88a699610dfbb8118b23c5ce205c530a7b0c7481b06ee95a8e4d0d66297ca34c18e0b9366c963ea3244f37d66a7fda0ec6ffaa084f2ae7568
+DIST rizin-testbins-b7d6c0ec57eb1c14e970b8301f36cbac997ee695.tar.gz 116758002 BLAKE2B f30412c8b749de7e71e71b472ce1237091e71fac15d08e6ab5a3bcd9b87fbf75e347427cb588d18b62376040061f90b9b78016db689e46e5b32d3fd2aac6f1bf SHA512 94aca148dc2aaede66c63253717b3ee5f34b46dc8a634d7a3916786c97075c6eb9ee98af25c2af2778a601ade7cfb1d41ed3b11de36ddb74abc5f4eabef74ef3

diff --git a/dev-util/rizin/rizin-0.1.2.ebuild b/dev-util/rizin/rizin-0.1.2.ebuild
new file mode 100644
index 00000000000..d1ca78992fe
--- /dev/null
+++ b/dev-util/rizin/rizin-0.1.2.ebuild
@@ -0,0 +1,60 @@
+# Copyright 1999-2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+# This is the commit that the CI for the release commit used
+BINS_COMMIT="b7d6c0ec57eb1c14e970b8301f36cbac997ee695"
+
+inherit meson
+
+DESCRIPTION="reverse engineering framework for binary analysis"
+HOMEPAGE="https://rizin.re/"
+
+SRC_URI="https://github.com/rizinorg/rizin/releases/download/v${PV}/rizin-src-${PV}.tar.xz
+	test? ( https://github.com/rizinorg/rizin-testbins/archive/${BINS_COMMIT}.tar.gz -> rizin-testbins-${BINS_COMMIT}.tar.gz )"
+KEYWORDS="~amd64"
+
+LICENSE="Apache-2.0 BSD LGPL-3 MIT"
+SLOT="0"
+IUSE="test"
+RESTRICT="!test? ( test )"
+
+RDEPEND="
+	sys-apps/file
+	app-arch/lz4:0=
+	dev-libs/capstone:0=
+	dev-libs/libuv:0=
+	dev-libs/libzip:0=
+	dev-libs/openssl:0=
+	dev-libs/tree-sitter
+	dev-libs/xxhash
+	sys-libs/zlib:0=
+"
+DEPEND="${RDEPEND}"
+
+src_prepare() {
+	default
+
+	if use test; then
+	   mv "${WORKDIR}/rizin-testbins-${BINS_COMMIT}" "${S}/test/bins" || die
+	fi
+}
+
+src_configure() {
+	local emesonargs=(
+		-Dcli=enabled
+		-Duse_sys_capstone=true
+		-Duse_sys_magic=true
+		-Duse_sys_zip=true
+		-Duse_sys_zlib=true
+		-Duse_sys_lz4=true
+		-Duse_sys_xxhash=true
+		-Duse_sys_openssl=true
+		-Duse_sys_tree_sitter=true
+
+		$(meson_use test enable_tests)
+		$(meson_use test enable_rz_test)
+	)
+	meson_src_configure
+}


             reply	other threads:[~2021-03-31 15:43 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 15:42 John Helmert III [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-26 14:00 [gentoo-commits] repo/gentoo:master commit in: dev-util/rizin/ Sam James
2025-07-22  0:44 John Helmert III
2025-02-09  2:54 John Helmert III
2025-02-01 23:08 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-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=1617205370.1216ea4d1ffae3bb3a94c31f4b513150eb86576d.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