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/libtracefs/
Date: Tue, 20 Dec 2022 01:56:26 +0000 (UTC)	[thread overview]
Message-ID: <1671501291.a7bf44d1d192283e7c202986c0112b066c3af5b8.dlan@gentoo> (raw)

commit:     a7bf44d1d192283e7c202986c0112b066c3af5b8
Author:     Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 19 03:11:39 2022 +0000
Commit:     Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Tue Dec 20 01:54:51 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a7bf44d1

dev-libs/libtracefs: Version bump 1.6.3

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

 dev-libs/libtracefs/Manifest                |  1 +
 dev-libs/libtracefs/libtracefs-1.6.3.ebuild | 53 +++++++++++++++++++++++++++++
 2 files changed, 54 insertions(+)

diff --git a/dev-libs/libtracefs/Manifest b/dev-libs/libtracefs/Manifest
index f22710e533da..90ef82213231 100644
--- a/dev-libs/libtracefs/Manifest
+++ b/dev-libs/libtracefs/Manifest
@@ -2,3 +2,4 @@ DIST libtracefs-1.3.1.tar.gz 175453 BLAKE2B d9801c9f50513a8b2d2de57f768aec69c3e4
 DIST libtracefs-1.4.2.tar.gz 178382 BLAKE2B a956423370077613417812ad18da284521e8798701d558f4e419af6c43bd8a06c489525bbab26e6bc5d5d5e8fd0e6a7322d34f976a4ea560670eb594818d07fc SHA512 4a66c3cf8050de5acc4c63996cbcfa2c014e26ad6011eb89b0cff47ffbd6343637009354edf6bb173b9fd08103012774376c33fd6f642741f7990f2d6de3ea0c
 DIST libtracefs-1.5.0.tar.gz 179569 BLAKE2B d69d4bb2c9cbf6dd971afaad280534ce8af4982ca76c7b12cb8432f56a01d622a5d58c827cfe86537e5db2a416ab1092c95309b77b766b183266e1ad22ad8d13 SHA512 5e936a788473c0eb373144231ef9ac139ae53b4685053dfed74157a9432d429f35b70290607679eae9f44fd858d2102a02c3beac35d8de35d856c3c1001644d3
 DIST libtracefs-1.6.1.tar.gz 193086 BLAKE2B 53f6740c7f06e1d618594e03ec7fbda273bbeb87bfda67acfad1e1670fd69670187c7267af1abcd1502c338499dc8d4ffe28a213b3ad17ff5a6e2b435c1c242f SHA512 9fa9b470869bdc0134cc72eb7a9e0131638c3416d24e403c7fc819d49a5e521ca8c852ece4ac87d6a744c32846a2567c44c1e3b8b329f77db2d89e57c9e36340
+DIST libtracefs-1.6.3.tar.gz 193859 BLAKE2B 89029e59590f4e25c5d39d5b638c381e966e8dee055bf7873492a6cdc8b1e1df90cad84a8db4e1abcacbc43fbb23c9fefbdb53123a409a19d07925e7a39efcdb SHA512 273d008644b5d205def79fa8c1db51f21327c02abee16dfc706cfa7ad421be111ac3280b2dd493a8be5f4d9f2fdcb471d7de17e6b3e56df7cb2f1a11b4e1bfaa

diff --git a/dev-libs/libtracefs/libtracefs-1.6.3.ebuild b/dev-libs/libtracefs/libtracefs-1.6.3.ebuild
new file mode 100644
index 000000000000..440403770349
--- /dev/null
+++ b/dev-libs/libtracefs/libtracefs-1.6.3.ebuild
@@ -0,0 +1,53 @@
+# Copyright 2019-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit toolchain-funcs
+
+DESCRIPTION="Linux kernel trace file system library"
+HOMEPAGE="https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/"
+
+if [[ ${PV} =~ [9]{4,} ]]; then
+	EGIT_REPO_URI="git://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/"
+	inherit git-r3
+else
+	SRC_URI="https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/snapshot/${P}.tar.gz"
+	KEYWORDS="~amd64 ~arm64 ~x86"
+fi
+
+LICENSE="LGPL-2.1"
+SLOT="0"
+IUSE="doc"
+RDEPEND="
+	>=dev-libs/libtraceevent-1.3.0
+"
+DEPEND="${RDEPEND}"
+# source-highlight is needed, see bug https://bugs.gentoo.org/865469
+BDEPEND="
+	virtual/pkgconfig
+	doc? ( app-text/xmlto app-text/asciidoc dev-util/source-highlight )
+"
+
+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)/libtracefs.a" || die
+	# install-doc is wrong target, see https://bugs.gentoo.org/865465
+	use doc && emake "${EMAKE_FLAGS[@]}" DESTDIR="${ED}" install_doc
+}


             reply	other threads:[~2022-12-20  1:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20  1:56 Yixun Lan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-31 21:29 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libtracefs/ Sam James
2024-10-30 15:46 Arthur Zamarin
2024-10-26  3:49 Sam James
2024-10-26  1:16 Sam James
2024-10-25 22:31 Sam James
2024-10-25 22:31 Sam James
2024-08-26  0:03 Yixun Lan
2024-08-23 12:35 Yixun Lan
2024-05-30  7:53 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-11  8:45 Yixun Lan
2024-02-04 21:42 Ionen Wolkens
2023-07-11 11:03 WANG Xuerui
2023-07-05 21:41 Sam James
2023-07-05 21:41 Sam James
2023-07-05 20:53 Sam James
2023-06-10  9:12 Sam James
2023-01-19 22:51 Yixun Lan
2023-01-19 22:51 Yixun Lan
2023-01-13  6:39 Sam James
2023-01-11  8:03 Arthur Zamarin
2022-12-22  6:12 Yixun Lan
2022-11-19  1:05 Yixun Lan
2022-10-08  1:54 Yixun Lan
2022-09-02 13:59 Yixun Lan
2022-08-18 18:43 Sam James
2022-07-29 12:12 Arthur Zamarin
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=1671501291.a7bf44d1d192283e7c202986c0112b066c3af5b8.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