public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/nio4r/
Date: Mon,  3 Apr 2023 00:47:52 +0000 (UTC)	[thread overview]
Message-ID: <1680482792.58fe36494c271d680df65d9d8b519d0426712949.sam@gentoo> (raw)

commit:     58fe36494c271d680df65d9d8b519d0426712949
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr  3 00:17:21 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr  3 00:46:32 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=58fe3649

dev-ruby/nio4r: add 2.5.9

Closes: https://bugs.gentoo.org/884259
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-ruby/nio4r/Manifest           |  1 +
 dev-ruby/nio4r/nio4r-2.5.9.ebuild | 31 +++++++++++++++++++++++++++++++
 2 files changed, 32 insertions(+)

diff --git a/dev-ruby/nio4r/Manifest b/dev-ruby/nio4r/Manifest
index 80d05987f8c6..ee049c38ccdd 100644
--- a/dev-ruby/nio4r/Manifest
+++ b/dev-ruby/nio4r/Manifest
@@ -1 +1,2 @@
 DIST nio4r-2.5.8.gem 121856 BLAKE2B be79548761f52abab632b8e4660ab8557946079a51fe7f30c346f4f656ed2f8d0c8f2f463ed76a89bd4278bdfc0a0646ff2b8e0a815f97750836cb0bb250b9ef SHA512 3942403147882380b86f42c54a6d4e92c4e85dd3c0b5b9f473a05fcf98c041853e21d11d0481d1973342b5a4bfb59e02cfd523a44e9e45c3740627a45f7f99c7
+DIST nio4r-2.5.9.gem 122368 BLAKE2B 4238e2963604539207e1adc7ee78430e4f501ea8b71d807ee4f3c44322d16612779777f11b76313aaad6d252321435854f5b4905f83a2fe03c9d71be20b7a718 SHA512 d1c52896f186d19eb089a94d74ccadb427e64c204af149aa83a5a4dda3f0edd1bd2bae94afd21fcd58e3c2b9e2c17278a18717c0905de80e45540d13eeefd9e5

diff --git a/dev-ruby/nio4r/nio4r-2.5.9.ebuild b/dev-ruby/nio4r/nio4r-2.5.9.ebuild
new file mode 100644
index 000000000000..a3db5042c074
--- /dev/null
+++ b/dev-ruby/nio4r/nio4r-2.5.9.ebuild
@@ -0,0 +1,31 @@
+# Copyright 1999-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+USE_RUBY="ruby27 ruby30 ruby31 ruby32"
+
+RUBY_FAKEGEM_RECIPE_TEST="rspec3"
+
+RUBY_FAKEGEM_RECIPE_DOC=""
+RUBY_FAKEGEM_EXTRADOC="CHANGES.md README.md"
+
+RUBY_FAKEGEM_EXTENSIONS=(ext/nio4r/extconf.rb)
+
+inherit ruby-fakegem
+
+DESCRIPTION="A high performance selector API for monitoring IO objects"
+HOMEPAGE="https://github.com/socketry/nio4r"
+
+LICENSE="MIT || ( BSD GPL-2 )"
+SLOT="2"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86 ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+IUSE=""
+
+# 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() {
+	sed -i -e '/[Bb]undler/d' spec/spec_helper.rb || die
+	sed -e '/extension/ s:^:#:' -i Rakefile || die
+}


             reply	other threads:[~2023-04-03  0:48 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03  0:47 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-30  6:17 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/nio4r/ Hans de Graaff
2024-10-29  6:25 Hans de Graaff
2024-10-29  6:25 Hans de Graaff
2024-10-06 13:30 Jakov Smolić
2024-10-06 11:18 Sam James
2024-07-15  8:33 Hans de Graaff
2024-03-21  6:42 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
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=1680482792.58fe36494c271d680df65d9d8b519d0426712949.sam@gentoo \
    --to=sam@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