From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdex/
Date: Sat, 17 Feb 2024 21:53:19 +0000 (UTC) [thread overview]
Message-ID: <1708206710.ad15ccf4f06744b9cf2d1afb96cd497002202542.leio@gentoo> (raw)
commit: ad15ccf4f06744b9cf2d1afb96cd497002202542
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 17 21:41:19 2024 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sat Feb 17 21:51:50 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ad15ccf4
dev-libs/libdex: keep eventfd and io_uring usage enabled by default
Upstream made it possible to disable mainly for testing that combination in
CI; having these enabled seems to be still strongly preferred for performance
and having a standard build.
Signed-off-by: Mart Raudsepp <leio <AT> gentoo.org>
dev-libs/libdex/libdex-0.4.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libdex/libdex-0.4.3.ebuild b/dev-libs/libdex/libdex-0.4.3.ebuild
index d0270f94ed5d..5e1d5e1fb424 100644
--- a/dev-libs/libdex/libdex-0.4.3.ebuild
+++ b/dev-libs/libdex/libdex-0.4.3.ebuild
@@ -12,7 +12,7 @@ LICENSE="LGPL-2.1+"
SLOT="0/1"
KEYWORDS="~amd64 ~arm64 ~x86"
-IUSE="eventfd gtk-doc +introspection liburing sysprof test vala"
+IUSE="+eventfd gtk-doc +introspection +liburing sysprof test vala"
REQUIRED_USE="
gtk-doc? ( introspection )
vala? ( introspection )
next reply other threads:[~2024-02-17 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 21:53 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-15 19:22 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdex/ Pacho Ramos
2024-04-07 5:55 Arthur Zamarin
2024-03-02 22:41 Mart Raudsepp
2024-02-17 21:53 Mart Raudsepp
2023-11-04 23:03 Mart Raudsepp
2023-10-26 15:54 Pacho Ramos
2023-09-17 1:43 Matt Turner
2023-09-01 15:13 Matt Turner
2023-08-21 3:43 Matt Turner
2023-05-05 9:01 Arthur Zamarin
2023-03-20 22:06 Matt Turner
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=1708206710.ad15ccf4f06744b9cf2d1afb96cd497002202542.leio@gentoo \
--to=leio@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