public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libtraceevent/
Date: Wed, 17 May 2023 12:32:32 +0000 (UTC)	[thread overview]
Message-ID: <1684326650.3d3d14611360ce0e2f6a41c1d71351a4e34a6001.dlan@gentoo> (raw)

commit:     3d3d14611360ce0e2f6a41c1d71351a4e34a6001
Author:     Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Wed May 17 12:30:50 2023 +0000
Commit:     Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Wed May 17 12:30:50 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3d3d1461

dev-libs/libtraceevent: add 1.7.2

Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>

 dev-libs/libtraceevent/Manifest                   |  1 +
 dev-libs/libtraceevent/libtraceevent-1.7.2.ebuild | 50 +++++++++++++++++++++++
 2 files changed, 51 insertions(+)

diff --git a/dev-libs/libtraceevent/Manifest b/dev-libs/libtraceevent/Manifest
index cb27f98d057e..3890bd078857 100644
--- a/dev-libs/libtraceevent/Manifest
+++ b/dev-libs/libtraceevent/Manifest
@@ -1,3 +1,4 @@
 DIST libtraceevent-1.6.3.tar.gz 140072 BLAKE2B 416fa68e2604c3cc71323171b084261e38f08f630a03afda0e2ecc4860c8b08dae10b2abaa2afae54d2b4e382720b43a6616a9ab8599759de102af918eeb24fc SHA512 8064eb18dda6fdbff020759ed92e785b87d34be9ebc30cb6085785edeb8d7252cabf8d33d8738a3ec407672a3d891884d0f0b4c551fce26c76fa8eaf61b9e2f5
 DIST libtraceevent-1.7.0.tar.gz 147876 BLAKE2B 0017315845f96b6d92a9d4f6e0f2de5e130324c3142b382284838ee52db8df5892b7e9394690391cc2215a29cc685401767b0e5b64a493d8b4793b1fbb8d10a2 SHA512 ecfdadf450cfc4cc0ea878089b2f0f2bab68987609a39341c665481e0716f2ab3d3441fae72163354ab8ceebef0648d873a81ec00ce38e00066a60a2ad1673a7
 DIST libtraceevent-1.7.1.tar.gz 148170 BLAKE2B 2d935035874e49b3fa73d513c424cab7b5686acf4a9151482d8bbc40a84c0baab8df811ebe37c85cb3bd851b04d343c5ffd585631f00a671f7ee26d20d7734ca SHA512 412b93109ccd6e1bdece52f9a10989a58ff5693144fd460c7ebaef0ebc4649fac95eea20c5f88aa2f23bdc59bf359a65ab23ab41c3a5b7c92df6e52225477093
+DIST libtraceevent-1.7.2.tar.gz 148242 BLAKE2B 03eae9ea7a8cdf6b015af95031d6fbe8638361f8b0db836f48e9ef47c814465fad583440f80f0103e08758712bd24f7562e1a8678ab24d4a1749a0b88efa7a85 SHA512 aa6d14e6d2e8e64c7d53ba9f93d47331d5f1b5a5a624891ec18a08b0d4e3e82f7845d29957bb3fe4360151bb5870a67c69d5cb1f758bb2956d946221f186546e

diff --git a/dev-libs/libtraceevent/libtraceevent-1.7.2.ebuild b/dev-libs/libtraceevent/libtraceevent-1.7.2.ebuild
new file mode 100644
index 000000000000..a572e944cacb
--- /dev/null
+++ b/dev-libs/libtraceevent/libtraceevent-1.7.2.ebuild
@@ -0,0 +1,50 @@
+# Copyright 2019-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit toolchain-funcs
+
+DESCRIPTION="Linux kernel trace event library"
+HOMEPAGE="https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/"
+
+if [[ ${PV} =~ [9]{4,} ]]; then
+	EGIT_REPO_URI="git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/"
+	inherit git-r3
+else
+	SRC_URI="https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/snapshot/${P}.tar.gz"
+	KEYWORDS="~amd64 ~arm64 ~riscv ~x86"
+fi
+
+LICENSE="LGPL-2.1"
+SLOT="0"
+IUSE="doc"
+
+RDEPEND="
+	!<dev-util/trace-cmd-3.0
+"
+BDEPEND="
+	doc? ( app-text/xmlto app-text/asciidoc )
+"
+
+src_configure() {
+	EMAKE_FLAGS=(
+		"prefix=${EPREFIX}/usr"
+		"libdir=${EPREFIX}/usr/$(get_libdir)"
+		"CC=$(tc-getCC)"
+		"AR=$(tc-getAR)"
+		VERBOSE=1
+	)
+}
+
+src_compile() {
+	emake "${EMAKE_FLAGS[@]}"
+	use doc && emake doc
+}
+
+src_install() {
+	emake "${EMAKE_FLAGS[@]}" DESTDIR="${ED}" install
+	# can't prevent installation of the static lib with parameters
+	rm "${ED}/usr/$(get_libdir)/libtraceevent.a" || die
+	use doc && emake "${EMAKE_FLAGS[@]}" DESTDIR="${ED}" install-doc
+}


             reply	other threads:[~2023-05-17 12:32 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 12:32 Yixun Lan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-26  7:18 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libtraceevent/ Arthur Zamarin
2025-04-26  3:40 Sam James
2025-04-26  2:56 Sam James
2025-04-26  1:45 Sam James
2025-04-26  1:25 Sam James
2024-11-01  3:12 Yixun Lan
2024-11-01  3:12 Yixun Lan
2024-10-27  6:50 Arthur Zamarin
2024-10-25 22:53 Sam James
2024-10-25 22:09 Sam James
2024-10-25 22:09 Sam James
2024-10-25 22:09 Sam James
2024-08-26  0:03 Yixun Lan
2024-08-23 12:35 Yixun Lan
2024-05-30  7:53 Yixun Lan
2024-05-30  1:51 Yixun Lan
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-04 21:42 Ionen Wolkens
2023-07-11 11:03 WANG Xuerui
2023-06-11 20:22 Arthur Zamarin
2023-06-11 19:20 Arthur Zamarin
2023-06-11 19:16 Arthur Zamarin
2023-06-10  9:12 Sam James
2023-06-10  9:12 Sam James
2023-06-10  9:12 Sam James
2023-05-17 12:32 Yixun Lan
2023-03-22  5:27 Sam James
2023-01-19 22:51 Yixun Lan
2023-01-12 23:35 Yixun Lan
2023-01-11  8:03 Arthur Zamarin
2022-12-22  6:12 Yixun Lan
2022-12-20  1:56 Yixun Lan
2022-10-08  1:54 Yixun Lan
2022-09-02 13:59 Yixun Lan
2022-09-02 13:59 Yixun Lan
2022-07-29 12:12 Arthur Zamarin
2022-06-16 22:54 Patrick McLean
2022-06-16 16:58 Patrick McLean

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=1684326650.3d3d14611360ce0e2f6a41c1d71351a4e34a6001.dlan@gentoo \
    --to=dlan@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