From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/async-rspec/
Date: Sun, 23 Oct 2022 10:01:01 +0000 (UTC) [thread overview]
Message-ID: <1666519237.2c36cc4b3a24cfb2220dd2c7b5a520d95e64d7b0.graaff@gentoo> (raw)
commit: 2c36cc4b3a24cfb2220dd2c7b5a520d95e64d7b0
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 23 10:00:14 2022 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Oct 23 10:00:37 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2c36cc4b
dev-ruby/async-rspec: apply ruby project policies
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/async-rspec/async-rspec-1.16.1.ebuild | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/dev-ruby/async-rspec/async-rspec-1.16.1.ebuild b/dev-ruby/async-rspec/async-rspec-1.16.1.ebuild
index c920dff8061b..12f48d519fe1 100644
--- a/dev-ruby/async-rspec/async-rspec-1.16.1.ebuild
+++ b/dev-ruby/async-rspec/async-rspec-1.16.1.ebuild
@@ -3,24 +3,26 @@
EAPI=8
-USE_RUBY="ruby26 ruby27 ruby30 ruby31"
+USE_RUBY="ruby27 ruby30 ruby31"
+
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/refs/tags/v${PV}.tar.gz -> ${P}.tar.gz"
+SRC_URI="https://github.com/socketry/async-rspec/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="MIT"
-SLOT="$(ver_cut 1)/$(ver_cut 1-2)"
+SLOT="$(ver_cut 1)"
KEYWORDS="~amd64 ~sparc"
IUSE=""
-ruby_add_rdepend ">=dev-ruby/rspec-3.0:3
- >=dev-ruby/rspec-files-1.0:1
- >=dev-ruby/rspec-memory-1.0:1
+ruby_add_rdepend "dev-ruby/rspec:3
+ dev-ruby/rspec-files:1
+ dev-ruby/rspec-memory:1
"
ruby_add_bdepend "test? (
@@ -30,5 +32,7 @@ ruby_add_bdepend "test? (
all_ruby_prepare() {
sed -i -E 's/require_relative "(.+)"/require File.expand_path("\1")/g' "${RUBY_FAKEGEM_GEMSPEC}" || die
- sed -i -E 's/require '"'"'covered\/rspec'"'"'//g' "spec/spec_helper.rb" || die
+
+ # Avoid dependency on unpackaged covered
+ sed -i -e '/covered/ s:^:#:' spec/spec_helper.rb || die
}
next reply other threads:[~2022-10-23 10:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 10:01 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-20 23:43 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/async-rspec/ Sam James
2025-05-18 12:13 Arthur Zamarin
2025-03-18 12:12 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
2023-04-03 0:47 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-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=1666519237.2c36cc4b3a24cfb2220dd2c7b5a520d95e64d7b0.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