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, 28 Dec 2017 06:34:03 +0000 (UTC)	[thread overview]
Message-ID: <1514442630.2c16b938876df1acea2cc68bc70cde33a18a03d2.graaff@gentoo> (raw)

commit:     2c16b938876df1acea2cc68bc70cde33a18a03d2
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 28 06:30:30 2017 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Thu Dec 28 06:30:30 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2c16b938

dev-ruby/nio4r: add 2.2.0

Package-Manager: Portage-2.3.13, Repoman-2.3.3

 dev-ruby/nio4r/Manifest           |  1 +
 dev-ruby/nio4r/nio4r-2.2.0.ebuild | 40 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 41 insertions(+)

diff --git a/dev-ruby/nio4r/Manifest b/dev-ruby/nio4r/Manifest
index 752247926e0..937167aae1c 100644
--- a/dev-ruby/nio4r/Manifest
+++ b/dev-ruby/nio4r/Manifest
@@ -1,3 +1,4 @@
 DIST nio4r-1.2.1.gem 94208 BLAKE2B 229c1c690004444a6701ad765af26e592b9dbdb3646f155dc2114ea677b40097c0158c615efb25506c2ae59316e4ecdd7ec8747bf4f18a3ec2ca1be6bf028b85 SHA512 3136863955bd6f4d489955bae9baf2fb527447c0e71dade1a05402f3e7c8570bf1dd9b8335d70d7303ec4df0a236b13e4ede74ce9154be00a108afcd7c6b7f40
 DIST nio4r-2.0.0.gem 99840 BLAKE2B a567b353eca9962472687934db3cc5ecdd095b51a0273607888cc9cbffaff9a0ae0f2fb87973de38dd7494645e99e96f913155985812015e068bf7f70b898658 SHA512 347afee015e673c8c878799b50affe155ad880608309162de2b4437c051a60feb902b44bc9f5ca5af6fb9e2f84a067410596eac68b1a39374a167205dadc1444
 DIST nio4r-2.1.0.gem 100352 BLAKE2B fbd2af1e25e555a59a411896a14811fc0372b0cdfc59e5b337221e91ce51f14ac2390dae1ec13a5df9230bc0d5d59f38b35a9eae4d49993a91ababc21e7ce35c SHA512 40fdc0453fb5c6ea275cdacf698b834d2ea198448cdac33dd6353780097cb4957c53c0bb1576e7d99d9362f1def596412cb3c78e0600d38664a8e8ff37018d65
+DIST nio4r-2.2.0.gem 101888 BLAKE2B b860169c4fd4b3747af5327554b808c74585f509b69664da3da1558487a2f0119b9d1b56718c5301a13b4b4ccf8a55a8b661900d8992f40a8128ddbc638b0d87 SHA512 9a9acaede13da07894edb7012f593bd2132296f2130cc2529cfbbad421aaa1e7b144403c9812e6ac8429cf6bb9e8c7e746acd86f2061dedf4cc14fb10fdaa7fe

diff --git a/dev-ruby/nio4r/nio4r-2.2.0.ebuild b/dev-ruby/nio4r/nio4r-2.2.0.ebuild
new file mode 100644
index 00000000000..f3875b6b791
--- /dev/null
+++ b/dev-ruby/nio4r/nio4r-2.2.0.ebuild
@@ -0,0 +1,40 @@
+# Copyright 1999-2017 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+
+USE_RUBY="ruby22 ruby23 ruby24"
+
+RUBY_FAKEGEM_RECIPE_TEST="rspec3"
+
+RUBY_FAKEGEM_TASK_DOC=""
+RUBY_FAKEGEM_EXTRADOC="CHANGES.md README.md"
+
+inherit ruby-fakegem
+
+DESCRIPTION="A high performance selector API for monitoring IO objects"
+HOMEPAGE="https://github.com/socketry/nio4r"
+
+LICENSE="MIT"
+SLOT="2"
+KEYWORDS="~amd64 ~arm ~ppc64 ~ppc-macos ~x64-macos ~x86-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
+
+ruby_add_bdepend "test? ( dev-ruby/rspec-retry )"
+
+all_ruby_prepare() {
+	sed -i -e '/[Cc]overalls/d' -e '/[Bb]undler/d' spec/spec_helper.rb || die
+	sed -e '/extension/ s:^:#:' -i Rakefile || die
+}
+
+each_ruby_configure() {
+	${RUBY} -Cext/${PN} extconf.rb || die
+}
+
+each_ruby_compile() {
+	emake V=1 -Cext/${PN}
+	cp ext/${PN}/*$(get_modname) lib/ || die
+}


             reply	other threads:[~2017-12-28  6:34 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28  6:34 Hans de Graaff [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
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-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=1514442630.2c16b938876df1acea2cc68bc70cde33a18a03d2.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