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/rjb/
Date: Sun, 26 Jul 2020 09:15:58 +0000 (UTC)	[thread overview]
Message-ID: <1595754951.66eff18d45c042bf4930ee1f2d7ea1a1265a0d35.graaff@gentoo> (raw)

commit:     66eff18d45c042bf4930ee1f2d7ea1a1265a0d35
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 26 08:53:33 2020 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Jul 26 09:15:51 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=66eff18d

dev-ruby/rjb: cleanup

Package-Manager: Portage-2.3.103, Repoman-2.3.23
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/rjb/Manifest         |  1 -
 dev-ruby/rjb/rjb-1.5.7.ebuild | 81 -------------------------------------------
 2 files changed, 82 deletions(-)

diff --git a/dev-ruby/rjb/Manifest b/dev-ruby/rjb/Manifest
index e589f78bd9b..3ebcdc99db8 100644
--- a/dev-ruby/rjb/Manifest
+++ b/dev-ruby/rjb/Manifest
@@ -1,2 +1 @@
-DIST rjb-1.5.7.gem 72704 BLAKE2B 9a4f2b304c05f65c0d78ca4909814da366de717f518017c73d23cfcf188d653141d6c4549200c4bd3e55421f59cf8442cf2d01c1c5c1be813964ee7fb4a7b501 SHA512 0ccdbb5bc6f9f5d914d5b117c96310d709965b81a4bd2d0d7c428aabf4e32672572d4187660bc1b509fa3c92ac4cbe97cbd98412253d4ec9a7e4981f3b7a3131
 DIST rjb-1.6.1.gem 74240 BLAKE2B 103e3885634be9c7dd842c2737c420511fea04e4e2d18f77dba7689c47da996fa37af5d08827de21ec38effd3fd99407e99491c8b99d134dded219ccf3880b79 SHA512 5b78fc4eabceddeb901145af39b1fc76e9a44801596ea4bacf9ce601cc109107cf042b1aa4c27049abd766ffca3206364079866ce7b88d25657fa75e7593adc3

diff --git a/dev-ruby/rjb/rjb-1.5.7.ebuild b/dev-ruby/rjb/rjb-1.5.7.ebuild
deleted file mode 100644
index c2f79b950d9..00000000000
--- a/dev-ruby/rjb/rjb-1.5.7.ebuild
+++ /dev/null
@@ -1,81 +0,0 @@
-# Copyright 1999-2018 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-USE_RUBY="ruby23 ruby24 ruby25 ruby26"
-
-RUBY_FAKEGEM_EXTRADOC="readme.txt ChangeLog"
-RUBY_FAKEGEM_RECIPE_DOC="rdoc"
-RUBY_FAKEGEM_TASK_TEST=""
-
-RUBY_FAKEGEM_EXTRAINSTALL="data"
-
-inherit java-pkg-2 ruby-ng ruby-fakegem
-
-DESCRIPTION="Rjb is a Ruby-Java software bridge"
-HOMEPAGE="https://github.com/arton/rjb"
-
-LICENSE="LGPL-2.1"
-SLOT="0"
-KEYWORDS="~amd64 ~x86"
-IUSE="examples hardened"
-
-DEPEND=">=virtual/jdk-1.5
-	hardened? ( sys-apps/paxctl )"
-RDEPEND="virtual/jre"
-
-pkg_setup() {
-	ruby-ng_pkg_setup
-	java-pkg-2_pkg_setup
-}
-
-all_ruby_prepare() {
-	# The console is not available for testing.
-	sed -i -e '/test_noarg_sinvoke/,/end/ s:^:#:' test/test.rb || die
-
-	# Avoid encoding tests since not all locales may be available.
-	sed -i -e '/test_kjconv/,/^  end/ s:^:#:' test/test.rb || die
-}
-
-each_ruby_prepare() {
-	#dev-lang/ruby might need the "hardened" flag to enforce the following:
-	if use hardened; then
-		paxctl -v /usr/bin/ruby 2>/dev/null | grep MPROTECT | grep disabled || ewarn '!!! rjb will only work if ruby is MPROTECT disabled\n  please disable it if required using paxctl -m /usr/bin/ruby'
-	fi
-	# force compilation of class file for our JVM
-	rm -rf data
-}
-
-each_ruby_configure() {
-	${RUBY} -C ext extconf.rb || die "extconf.rb failed"
-}
-
-each_ruby_compile() {
-	emake V=1 -C ext CFLAGS="${CFLAGS} -fPIC" archflags="${LDFLAGS}"
-}
-
-each_ruby_install() {
-	each_fakegem_install
-
-	# currently no elegant way to do this (bug #352765)
-	ruby_fakegem_newins ext/rjbcore.so lib/rjbcore.so
-
-	if use examples; then
-		insinto /usr/share/doc/${PF}
-		doins -r samples
-	fi
-}
-
-each_ruby_test() {
-	if use hardened; then
-		paxctl -v ${RUBY} 2>/dev/null | grep MPROTECT | grep -q disabled
-		if [ $? = 0 ]; then
-			${RUBY} -C test -I../lib:.:../ext test.rb || die
-		else
-			ewarn "${RUBY} has MPROTECT enabled, rjb will not work until it is disabled, skipping tests."
-		fi
-	else
-		${RUBY} -C test -I../lib:.:../ext test.rb || die
-	fi
-}


             reply	other threads:[~2020-07-26  9:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26  9:15 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-31  9:38 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rjb/ Hans de Graaff
2024-09-07  8:29 Hans de Graaff
2024-03-04 18:33 Rick Farina
2024-02-17  9:00 Hans de Graaff
2023-12-27 12:26 Hans de Graaff
2023-12-27 12:26 Hans de Graaff
2023-11-10  5:54 Hans de Graaff
2023-09-28  4:38 Hans de Graaff
2023-07-10 18:10 Hans de Graaff
2023-03-31  1:03 Sam James
2023-02-18  7:29 Hans de Graaff
2022-12-28  7:18 Hans de Graaff
2022-12-04 10:14 Hans de Graaff
2022-04-08  9:15 Hans de Graaff
2021-05-02  5:46 Hans de Graaff
2021-04-18  7:57 Hans de Graaff
2021-04-18  7:57 Hans de Graaff
2021-02-09  5:47 Hans de Graaff
2020-09-15  5:09 Hans de Graaff
2020-02-05  6:16 Hans de Graaff
2019-11-06 18:11 Rick Farina
2019-11-02  8:51 Hans de Graaff
2019-11-02  5:40 Hans de Graaff
2018-12-28  7:25 Hans de Graaff
2018-02-10  7:42 Hans de Graaff
2017-08-24  5:49 Hans de Graaff
2017-08-24  5:49 Hans de Graaff
2016-10-30  6:42 Hans de Graaff
2016-03-28 22:05 Manuel Rüger
2015-11-29  7:29 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=1595754951.66eff18d45c042bf4930ee1f2d7ea1a1265a0d35.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