public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/eventmachine/
Date: Wed, 29 Mar 2023 13:04:52 +0000 (UTC)	[thread overview]
Message-ID: <1680094594.a6ecdab26407dfb04c23f3cbc53487b23e4c028a.sam@gentoo> (raw)

commit:     a6ecdab26407dfb04c23f3cbc53487b23e4c028a
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 29 11:51:09 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar 29 12:56:34 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a6ecdab2

dev-ruby/eventmachine: drop 1.2.7-r3

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-ruby/eventmachine/eventmachine-1.2.7-r3.ebuild | 85 ----------------------
 1 file changed, 85 deletions(-)

diff --git a/dev-ruby/eventmachine/eventmachine-1.2.7-r3.ebuild b/dev-ruby/eventmachine/eventmachine-1.2.7-r3.ebuild
deleted file mode 100644
index 268f40c9d2c3..000000000000
--- a/dev-ruby/eventmachine/eventmachine-1.2.7-r3.ebuild
+++ /dev/null
@@ -1,85 +0,0 @@
-# Copyright 1999-2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-USE_RUBY="ruby26 ruby27"
-
-RUBY_FAKEGEM_RECIPE_DOC="rdoc"
-RUBY_FAKEGEM_DOCDIR="rdoc"
-RUBY_FAKEGEM_EXTRADOC="docs/*.md CHANGELOG.md README.md"
-
-RUBY_FAKEGEM_GEMSPEC="eventmachine.gemspec"
-
-RUBY_FAKEGEM_EXTENSIONS=(ext/extconf.rb ext/fastfilereader/extconf.rb)
-RUBY_FAKEGEM_EXTRAINSTALL=(examples)
-
-inherit ruby-fakegem
-
-DESCRIPTION="EventMachine is a fast, simple event-processing library for Ruby programs"
-HOMEPAGE="https://github.com/eventmachine/eventmachine"
-SRC_URI="https://github.com/eventmachine/eventmachine/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-# Collection of upstream patches to fix compatibility with newer OpenSSL
-SRC_URI+=" https://dev.gentoo.org/~sam/distfiles/${CATEGORY}/${PN}/${P}-openssl-patches.tar.bz2"
-
-LICENSE="|| ( GPL-2 Ruby-BSD )"
-SLOT="0"
-KEYWORDS="amd64 ~arm64 ~ppc ~ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris ~x86-solaris"
-IUSE="test"
-RESTRICT="!test? ( test )"
-
-DEPEND="${DEPEND}
-	dev-libs/openssl:0="
-RDEPEND="${RDEPEND}
-	dev-libs/openssl:0="
-
-ruby_add_bdepend "test? ( dev-ruby/test-unit:2 )"
-
-PATCHES=(
-	# Collection of upstream patches (rebased by Fedora, thanks!) to
-	# fix (mostly test) compatibility with >= OpenSSL 1.1.1.
-	"${WORKDIR}"/all/patches/
-)
-
-all_ruby_prepare() {
-	# Remove package tasks to avoid dependency on rake-compiler.
-	rm rakelib/package.rake || die
-
-	sed -i -e '/git ls-files/d' ${RUBY_FAKEGEM_GEMSPEC} || die
-	# Remove the resolver tests since they require network access and
-	# the localhost test fails with an IPv6 localhost.
-	rm tests/test_resolver.rb || die
-
-	# Needs a tty
-	rm tests/test_kb.rb || die
-
-	# Avoid tests that require network access
-	sed -e '/test_bind_connect/,/^  end/ s:^:#:' \
-		-e '/test_invalid_address_bind_connect_src/,/^  end/ s:^:#:' \
-		-e '/test_invalid_address_bind_connect_dst/,/^  end/ s:^:#:' \
-		-i tests/test_basic.rb || die
-	sed -e '/test_ipv6_udp_local_server/,/^    end/ s:^:#:' \
-		-e '/test_ipv6_tcp_local_server/,/^    end/ s:^:#:' \
-		-i tests/test_ipv6.rb || die
-	sed -e '/test_for_real/,/^    end/ s:^:#:' -i tests/test_pending_connect_timeout.rb || die
-	sed -e '/test_connect_timeout/,/^  end/ s:^:#:' -i tests/test_unbind_reason.rb || die
-	sed -e '/test_cookie/,/^  end/ s:^:#:' \
-		-e '/test_http_client/,/^  end/ s:^:#:' \
-		-e '/test_version_1_0/,/^  end/ s:^:#:' \
-		-i tests/test_httpclient.rb || die
-	sed -e '/test_get/,/^  end/ s:^:#:' \
-		-e '/test_https_get/,/^  end/ s:^:#:' \
-		-i tests/test_httpclient2.rb || die
-
-	# Avoid test that deliberately triggers a C++ exception which causes
-	# a SEGFAULT. This does not appear to happen upstream (on travis).
-	rm tests/test_exc.rb || die
-}
-
-each_ruby_test() {
-	${RUBY} -Ilib -S testrb-2 tests/test_*.rb || die
-}
-
-all_ruby_install() {
-	all_fakegem_install
-}


             reply	other threads:[~2023-03-29 13:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 13:04 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-29 11:48 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/eventmachine/ Sam James
2023-03-29 11:38 Sam James
2023-03-12 12:09 Hans de Graaff
2022-07-30  7:46 Hans de Graaff
2022-06-26  6:44 Hans de Graaff
2022-06-18 20:25 Sam James
2022-06-18 20:25 Sam James
2021-09-28 19:34 Sam James
2021-09-28  1:09 Sam James
2021-09-28  1:08 Sam James
2021-09-28  1:01 Sam James
2021-06-22 18:19 Sam James
2020-05-23  6:34 Hans de Graaff
2019-02-02 10:36 Hans de Graaff
2018-07-15 19:05 Hans de Graaff
2018-07-15 19:05 Hans de Graaff
2018-05-18  5:56 Hans de Graaff
2018-04-26  4:57 Hans de Graaff
2018-04-17 18:29 Hans de Graaff
2018-04-16 18:32 Hans de Graaff
2018-02-25  7:47 Hans de Graaff
2018-02-25  6:47 Hans de Graaff
2016-06-26  5:38 Hans de Graaff
2016-03-17 11:56 Agostino Sarubbo
2016-03-17  6:39 Hans de Graaff
2016-03-17  6:39 Hans de Graaff
2016-03-17  6:39 Hans de Graaff
2016-01-14 20:37 Manuel Rüger
2016-01-14 20:37 Manuel Rüger
2015-10-03  9:12 Hans de Graaff

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=1680094594.a6ecdab26407dfb04c23f3cbc53487b23e4c028a.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