From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/coderay/
Date: Sat, 19 Sep 2020 05:35:58 +0000 (UTC) [thread overview]
Message-ID: <1600493729.e5ac10eb1958a81336226c9020fdec065c1cfb29.graaff@gentoo> (raw)
commit: e5ac10eb1958a81336226c9020fdec065c1cfb29
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Fri Sep 18 08:24:32 2020 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Sep 19 05:35:29 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e5ac10eb
dev-ruby/coderay: also run specs
Package-Manager: Portage-3.0.4, Repoman-3.0.1
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/coderay/coderay-1.1.3-r1.ebuild | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/dev-ruby/coderay/coderay-1.1.3-r1.ebuild b/dev-ruby/coderay/coderay-1.1.3-r1.ebuild
index cf223d7b17d..1cc2fec61d4 100644
--- a/dev-ruby/coderay/coderay-1.1.3-r1.ebuild
+++ b/dev-ruby/coderay/coderay-1.1.3-r1.ebuild
@@ -7,7 +7,7 @@ USE_RUBY="ruby24 ruby25 ruby26 ruby27"
# The test target also contains test:exe but that requires
# shoulda-context which we do not have packaged yet.
-RUBY_FAKEGEM_TASK_TEST="test:functional test:units"
+RUBY_FAKEGEM_TASK_TEST="spec test:functional test:units"
RUBY_FAKEGEM_TASK_DOC="doc"
RUBY_FAKEGEM_DOCDIR="doc"
@@ -32,6 +32,8 @@ IUSE=""
# bootstrapping rspec with new versions easier, since redcloth depends
# on rake-compiler.
+ruby_add_bdepend "test? ( dev-ruby/rspec:3 )"
+
all_ruby_prepare() {
sed -i -e "/[Bb]undler/d" Rakefile || die
sed -i -e '/git ls-files/ s:^:#:' -e 's/.rc.*"/"/' coderay.gemspec || die
next reply other threads:[~2020-09-19 5:36 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 5:35 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-30 7:43 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/coderay/ Hans de Graaff
2023-07-14 5:46 Arthur Zamarin
2023-03-10 9:08 Hans de Graaff
2023-01-21 9:08 Hans de Graaff
2022-12-18 10:18 Sam James
2022-12-18 10:18 Sam James
2022-12-18 10:18 Sam James
2022-12-18 10:06 Sam James
2022-12-18 10:06 Sam James
2022-12-18 10:06 Sam James
2022-12-18 10:06 Sam James
2022-05-08 16:12 WANG Xuerui
2022-03-31 5:39 Hans de Graaff
2021-08-02 21:48 Marek Szuba
2021-03-09 6:51 Hans de Graaff
2020-06-06 9:02 Hans de Graaff
2020-06-02 4:49 Hans de Graaff
2019-12-26 15:41 Hans de Graaff
2019-03-30 19:50 Mikle Kolyada
2018-12-28 11:13 Hans de Graaff
2017-12-26 7:06 Hans de Graaff
2017-12-25 7:05 Hans de Graaff
2017-12-24 8:49 Markus Meier
2017-11-30 20:06 Sergei Trofimovich
2017-11-30 20:06 Sergei Trofimovich
2017-11-27 8:50 Sergei Trofimovich
2017-11-26 13:25 Hans de Graaff
2017-10-23 18:42 Thomas Deutschmann
2017-10-22 21:42 Tobias Klausmann
2017-10-22 7:11 Hans de Graaff
2017-10-21 10:19 Sergei Trofimovich
2017-10-21 9:10 Sergei Trofimovich
2017-10-21 7:27 Hans de Graaff
2017-09-04 5:22 Hans de Graaff
2017-08-23 21:43 Sergei Trofimovich
2017-06-28 9:35 Alexis Ballier
2016-12-28 8:14 Hans de Graaff
2016-11-25 10:10 Hans de Graaff
2016-10-02 9:22 Jeroen Roovers
2016-05-26 14:39 Tobias Klausmann
2016-04-10 0:01 Manuel Rüger
2016-03-17 10:50 Agostino Sarubbo
2016-03-15 14:40 Agostino Sarubbo
2016-03-13 12:34 Markus Meier
2016-03-07 21:14 Hans de Graaff
2016-02-21 11:19 Manuel Rüger
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=1600493729.e5ac10eb1958a81336226c9020fdec065c1cfb29.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