From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/async-rspec/
Date: Mon, 3 Apr 2023 00:47:51 +0000 (UTC) [thread overview]
Message-ID: <1680482787.ca906ed922ef32e0580b1ab1b1c6439e1abc0c64.sam@gentoo> (raw)
commit: ca906ed922ef32e0580b1ab1b1c6439e1abc0c64
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 2 23:09:38 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr 3 00:46:27 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ca906ed9
dev-ruby/async-rspec: enable ruby32
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ruby/async-rspec/async-rspec-1.16.1-r1.ebuild | 38 +++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/dev-ruby/async-rspec/async-rspec-1.16.1-r1.ebuild b/dev-ruby/async-rspec/async-rspec-1.16.1-r1.ebuild
new file mode 100644
index 000000000000..08d625635a1d
--- /dev/null
+++ b/dev-ruby/async-rspec/async-rspec-1.16.1-r1.ebuild
@@ -0,0 +1,38 @@
+# Copyright 2022-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_EXTRADOC="README.md"
+RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
+
+inherit ruby-fakegem
+
+DESCRIPTION="Helpers for writing specs against the async gem"
+HOMEPAGE="https://github.com/socketry/async-rspec"
+SRC_URI="https://github.com/socketry/async-rspec/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="$(ver_cut 1)"
+KEYWORDS="~amd64"
+IUSE=""
+
+ruby_add_rdepend "dev-ruby/rspec:3
+ dev-ruby/rspec-files:1
+ dev-ruby/rspec-memory:1
+"
+
+ruby_add_bdepend "test? (
+ dev-ruby/async
+ dev-ruby/async-io
+)"
+
+all_ruby_prepare() {
+ sed -i -E 's/require_relative "(.+)"/require File.expand_path("\1")/g' "${RUBY_FAKEGEM_GEMSPEC}" || die
+
+ # Avoid dependency on unpackaged covered
+ sed -i -e '/covered/ s:^:#:' spec/spec_helper.rb || die
+}
next reply other threads:[~2023-04-03 0:47 UTC|newest]
Thread overview: 23+ 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 --
2025-03-18 12:12 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/async-rspec/ Hans de Graaff
2024-02-25 9:01 Hans de Graaff
2023-12-30 9:28 Hans de Graaff
2023-10-24 9:30 Arthur Zamarin
2023-07-12 19:55 Hans de Graaff
2023-07-04 20:19 Sam James
2023-07-04 20:19 Sam James
2023-06-19 4:41 Hans de Graaff
2023-04-11 17:52 Jakov Smolić
2023-04-09 2:34 Sam James
2023-04-07 8:39 Sam James
2023-04-07 8:39 Sam James
2023-04-07 8:36 Sam James
2023-04-03 3:17 Sam James
2023-04-03 3:17 Sam James
2023-04-03 3:17 Sam James
2022-12-05 20:03 Arthur Zamarin
2022-12-01 4:03 Sam James
2022-12-01 4:03 Sam James
2022-12-01 2:04 Sam James
2022-10-23 10:01 Hans de Graaff
2022-10-22 21:33 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=1680482787.ca906ed922ef32e0580b1ab1b1c6439e1abc0c64.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