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/rest-client/
Date: Mon,  7 May 2018 05:02:32 +0000 (UTC)	[thread overview]
Message-ID: <1525669334.b4223f84a25c082a42d9847327efcf658c3c8145.graaff@gentoo> (raw)

commit:     b4223f84a25c082a42d9847327efcf658c3c8145
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon May  7 04:49:22 2018 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon May  7 05:02:14 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b4223f84

dev-ruby/rest-client: fix building without FEATURES=test

Use the default rdoc method to generate documentation
to avoid needing rspec with only USE=doc

Closes: https://bugs.gentoo.org/654864
Package-Manager: Portage-2.3.24, Repoman-2.3.6

 dev-ruby/rest-client/rest-client-2.0.2.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/dev-ruby/rest-client/rest-client-2.0.2.ebuild b/dev-ruby/rest-client/rest-client-2.0.2.ebuild
index 0a7ca052e8b..4b8540bc007 100644
--- a/dev-ruby/rest-client/rest-client-2.0.2.ebuild
+++ b/dev-ruby/rest-client/rest-client-2.0.2.ebuild
@@ -6,6 +6,7 @@ USE_RUBY="ruby22 ruby23 ruby24"
 
 RUBY_FAKEGEM_RECIPE_TEST="rspec3"
 
+RUBY_FAKEGEM_RECIPE_DOC="rdoc"
 RUBY_FAKEGEM_EXTRADOC="history.md README.md"
 
 inherit ruby-fakegem


             reply	other threads:[~2018-05-07  5:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07  5:02 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-17  5:57 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rest-client/ Hans de Graaff
2023-08-27 10:16 Jakov Smolić
2023-08-26 13:47 Arthur Zamarin
2023-08-26 13:30 Sam James
2023-08-13  8:40 Hans de Graaff
2023-01-25  7:30 Hans de Graaff
2022-12-04 10:14 Hans de Graaff
2022-08-17 15:39 Sam James
2022-07-29  4:48 Hans de Graaff
2022-07-26  9:49 Hans de Graaff
2021-02-22  6:49 Hans de Graaff
2020-04-18  5:44 Hans de Graaff
2020-01-12  8:35 Hans de Graaff
2019-10-13  8:17 Hans de Graaff
2019-10-13  7:59 Hans de Graaff
2019-05-05  7:28 Hans de Graaff
2019-01-16 19:01 Hans de Graaff
2018-11-23 10:46 Hans de Graaff
2018-06-25 18:44 Hans de Graaff
2018-05-09  4:26 Hans de Graaff
2018-04-29  9:42 Hans de Graaff
2018-03-02 10:43 Hans de Graaff
2017-06-28  6:09 Hans de Graaff
2017-04-26  4:59 Hans de Graaff
2017-04-26  4:59 Hans de Graaff
2017-04-21  5:07 Hans de Graaff
2017-02-21  7:29 Hans de Graaff
2016-12-25 20:44 Manuel Rüger
2016-11-27  8:29 Hans de Graaff
2016-11-27  8:29 Hans de Graaff
2016-11-25 14:49 Hans de Graaff
2016-10-15  9:18 Hans de Graaff
2016-08-05 12:14 Hans de Graaff
2016-08-05 12:14 Hans de Graaff
2016-07-28  6:06 Hans de Graaff
2016-04-17 11:24 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=1525669334.b4223f84a25c082a42d9847327efcf658c3c8145.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