public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/nio4r/
Date: Thu, 21 Mar 2024 06:42:18 +0000 (UTC)	[thread overview]
Message-ID: <1711003325.f16d075ecca4a91dee305fc29d7d2256b5ceda44.graaff@gentoo> (raw)

commit:     f16d075ecca4a91dee305fc29d7d2256b5ceda44
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 21 06:41:51 2024 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Thu Mar 21 06:42:05 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f16d075e

dev-ruby/nio4r: add 2.7.1

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/nio4r/Manifest           |  1 +
 dev-ruby/nio4r/nio4r-2.7.1.ebuild | 34 ++++++++++++++++++++++++++++++++++
 2 files changed, 35 insertions(+)

diff --git a/dev-ruby/nio4r/Manifest b/dev-ruby/nio4r/Manifest
index 3ac33138ca41..64efc36e79ed 100644
--- a/dev-ruby/nio4r/Manifest
+++ b/dev-ruby/nio4r/Manifest
@@ -1,3 +1,4 @@
 DIST nio4r-2.5.9.gem 122368 BLAKE2B 4238e2963604539207e1adc7ee78430e4f501ea8b71d807ee4f3c44322d16612779777f11b76313aaad6d252321435854f5b4905f83a2fe03c9d71be20b7a718 SHA512 d1c52896f186d19eb089a94d74ccadb427e64c204af149aa83a5a4dda3f0edd1bd2bae94afd21fcd58e3c2b9e2c17278a18717c0905de80e45540d13eeefd9e5
 DIST nio4r-2.6.1.gem 123904 BLAKE2B 5fbfe2a67fbd9fb6f49607358827391a56760c79435748f8fca0cbe6408f145cba224641b77afa8f6f49b1cd7e2fdd93e46e5aa3c75496f6539d66216ec3430b SHA512 bebf7f737f5e63107d77c4237a5750aa10f9bd1136deaa6bb1a8e5cab703d425a3a94a8f617df144e603f4f1f85ef62852740604a981e7dda41f0c43ae250406
 DIST nio4r-2.7.0.gem 124416 BLAKE2B f02a16cf45dc2ea547dd8e036ddff5c37c24e9188db9ab4f817a55243f87f78264ed11bcd8d055e244c655aea08fa4922cd53dcae39e090031c87d0d78909c7b SHA512 aeb0bd3e727fa6999a314cd2b15a35035694f41294f7e9c406a72fd50a7a7a02311efec8c5795a116fd3793bf6b81e17d884e156b844722933e45d056f0cbeb9
+DIST nio4r-2.7.1.gem 124416 BLAKE2B 4ae03731b0ae51bc51cfd12049e4d9beb9141feeb4196edafb26dd5ea4cc88e3cecaf0b121cd28c142cb509f991d22af5befe593443f7ecc420eb403fa83c0a1 SHA512 acade5696fe343b92f35f4bcfb7fbda48c8d9bbacff8e0571cffa193ade48d0c8f184db3480084bf3d796e5bd9176b285be4a52e4470c406bf867f538f1bfd4a

diff --git a/dev-ruby/nio4r/nio4r-2.7.1.ebuild b/dev-ruby/nio4r/nio4r-2.7.1.ebuild
new file mode 100644
index 000000000000..71be4cfe731f
--- /dev/null
+++ b/dev-ruby/nio4r/nio4r-2.7.1.ebuild
@@ -0,0 +1,34 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+USE_RUBY="ruby31 ruby32 ruby33"
+
+RUBY_FAKEGEM_RECIPE_TEST="rspec3"
+
+RUBY_FAKEGEM_RECIPE_DOC=""
+RUBY_FAKEGEM_EXTRADOC="changes.md readme.md"
+
+RUBY_FAKEGEM_EXTENSIONS=(ext/nio4r/extconf.rb)
+
+inherit flag-o-matic ruby-fakegem
+
+DESCRIPTION="A high performance selector API for monitoring IO objects"
+HOMEPAGE="https://github.com/socketry/nio4r"
+
+LICENSE="MIT || ( BSD GPL-2 )"
+SLOT="$(ver_cut 1)"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86 ~ppc-macos ~x64-macos ~x64-solaris"
+
+# Note that nio4r bundles a patched copy of libev, and without these
+# patches the tests fail: https://github.com/celluloid/nio4r/issues/15
+
+all_ruby_prepare() {
+	# See bug #855869 and its large number of dupes in bundled libev copies.
+	filter-lto
+	append-flags -fno-strict-aliasing
+
+	sed -i -e '/[Bb]undler/d' spec/spec_helper.rb || die
+	sed -e '/extension/ s:^:#:' -i Rakefile || die
+}


             reply	other threads:[~2024-03-21  6:42 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21  6:42 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-06 13:30 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/nio4r/ Jakov Smolić
2024-10-06 11:18 Sam James
2024-07-15  8:33 Hans de Graaff
2024-02-29  0:50 Sam James
2023-12-31 14:36 Hans de Graaff
2023-12-31 14:36 Hans de Graaff
2023-12-01  6:18 Hans de Graaff
2023-11-21  6:40 Hans de Graaff
2023-11-17  7:46 Hans de Graaff
2023-11-17  7:46 Hans de Graaff
2023-04-03  0:47 Sam James
2023-04-03  0:47 Sam James
2022-12-03  7:43 Hans de Graaff
2022-04-02  8:03 Agostino Sarubbo
2022-03-31 12:33 Jakov Smolić
2022-03-31  6:15 Hans de Graaff
2021-11-08  2:51 Yixun Lan
2021-10-28  5:27 Hans de Graaff
2021-08-04  6:41 Hans de Graaff
2021-05-10  4:35 Hans de Graaff
2021-03-04  6:55 Hans de Graaff
2021-02-13  7:55 Hans de Graaff
2021-02-06  6:59 Hans de Graaff
2021-02-04  7:58 Agostino Sarubbo
2021-02-03 23:55 Thomas Deutschmann
2021-02-03  6:45 Hans de Graaff
2020-09-16  5:55 Hans de Graaff
2020-09-11  5:14 Hans de Graaff
2020-09-08  5:48 Hans de Graaff
2020-09-05  8:01 Hans de Graaff
2020-05-31  8:19 Sergei Trofimovich
2020-04-25 12:44 Sergei Trofimovich
2020-04-15 21:49 Sergei Trofimovich
2020-04-14 21:06 Sergei Trofimovich
2020-02-29  6:00 Hans de Graaff
2020-02-29  6:00 Hans de Graaff
2019-09-25  6:11 Hans de Graaff
2019-08-29  5:24 Hans de Graaff
2019-08-29  5:24 Hans de Graaff
2019-08-28  5:15 Hans de Graaff
2019-07-24 23:16 Aaron Bauman
2019-07-08  4:24 Hans de Graaff
2019-01-31  7:35 Hans de Graaff
2019-01-31  7:35 Hans de Graaff
2018-05-03  4:48 Hans de Graaff
2018-04-19 19:37 Hans de Graaff
2018-04-19 19:37 Hans de Graaff
2018-03-25 17:58 Sergei Trofimovich
2018-03-18  6:25 Hans de Graaff
2018-02-07  5:52 Thomas Deutschmann
2017-12-28  6:34 Hans de Graaff
2017-09-12  8:18 Sergei Trofimovich
2017-08-26  8:27 Hans de Graaff
2017-08-26  8:27 Hans de Graaff
2017-06-21  7:27 Hans de Graaff
2017-05-29  4:31 Hans de Graaff
2017-04-16  6:40 Hans de Graaff
2017-01-31  7:05 Hans de Graaff
2016-07-21 17:36 Hans de Graaff
2016-03-22 21:58 Manuel Rüger
2016-02-02  6:25 Hans de Graaff
2015-12-24  6:37 Hans de Graaff
2015-12-24  6:37 Hans de Graaff
2015-12-06  7:05 Hans de Graaff
2015-12-05 13:01 Markus Meier

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=1711003325.f16d075ecca4a91dee305fc29d7d2256b5ceda44.graaff@gentoo \
    --to=graaff@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