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/fakeweb/
Date: Mon, 14 Nov 2016 06:39:01 +0000 (UTC)	[thread overview]
Message-ID: <1479104941.c38ad61b5abe67df32d547ff3b18d88313357449.graaff@gentoo> (raw)

commit:     c38ad61b5abe67df32d547ff3b18d88313357449
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 14 06:29:01 2016 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Nov 14 06:29:01 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c38ad61b

dev-ruby/fakeweb: cleanup

Package-Manager: portage-2.3.0

 dev-ruby/fakeweb/fakeweb-1.3.0-r1.ebuild | 53 --------------------------------
 1 file changed, 53 deletions(-)

diff --git a/dev-ruby/fakeweb/fakeweb-1.3.0-r1.ebuild b/dev-ruby/fakeweb/fakeweb-1.3.0-r1.ebuild
deleted file mode 100644
index 77cea55..00000000
--- a/dev-ruby/fakeweb/fakeweb-1.3.0-r1.ebuild
+++ /dev/null
@@ -1,53 +0,0 @@
-# Copyright 1999-2016 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-# $Id$
-
-EAPI=5
-
-USE_RUBY="ruby20"
-
-RUBY_FAKEGEM_DOCDIR="html"
-RUBY_FAKEGEM_EXTRADOC="CHANGELOG README.rdoc"
-
-inherit ruby-fakegem
-
-DESCRIPTION="Helper for faking web requests in Ruby"
-HOMEPAGE="https://github.com/chrisk/fakeweb"
-
-LICENSE="GPL-2"
-SLOT="0"
-KEYWORDS="amd64 ~arm ~ppc ~ppc64 ~x86"
-IUSE=""
-
-ruby_add_bdepend "
-	test? (
-		dev-ruby/mocha:0.13
-		dev-ruby/test-unit
-		dev-ruby/samuel
-		dev-ruby/right_http_connection
-	)"
-
-all_ruby_prepare() {
-	# The package bundles samuel and right_http_connection, remove
-	# them and use the packages instead.
-	rm -r test/vendor || die "failed to remove bundled gems"
-
-	# We don't package sdoc and we don't have the direct template.
-	sed -i -e 's/sdoc/rdoc/' -e '/template/d' Rakefile || die
-
-	# Require an old enough version of mocha
-	sed -i -e '1igem "mocha", "~> 0.13.0"' test/test_helper.rb || die
-
-	# Use the test-unit gem to make jruby compatible with newer mocha.
-	sed -i -e '1igem "test-unit"' test/test_helper.rb || die
-}
-
-each_ruby_prepare() {
-	case ${RUBY} in
-		*ruby2[01])
-			# Tests fail on mocking of TCPSocket, but fakeweb itself
-			# actually works as evidenced by the thor test suite.
-			rm test/test_fake_web_open_uri.rb test/test_allow_net_connect.rb test/test_fake_web.rb || die
-			;;
-	esac
-}


             reply	other threads:[~2016-11-14  6:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14  6:39 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-10  6:17 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/fakeweb/ Hans de Graaff
2020-05-23  5:28 Hans de Graaff
2019-02-01 11:46 Hans de Graaff
2018-11-13  6:11 Hans de Graaff
2018-06-27  5:23 Hans de Graaff
2018-04-25  5:23 Hans de Graaff
2017-07-30  6:10 Hans de Graaff
2017-06-26 18:39 Hans de Graaff
2017-04-29 20:13 Jeroen Roovers
2017-04-17  6:45 Hans de Graaff
2016-11-13  9:16 Hans de Graaff
2016-09-28  8:17 Tobias Klausmann
2016-04-03 21:44 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=1479104941.c38ad61b5abe67df32d547ff3b18d88313357449.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