[gentoo-commits] repo/gentoo:master commit in: dev-ruby/bcrypt-ruby/

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/bcrypt-ruby/
Date: Tue, 12 Jul 2022 21:01:34 +0000 (UTC)	[thread overview]
Message-ID: <1657659689.a2664e70597e36d3e50f9f92ea3260439ae20478.graaff@gentoo> (raw)

commit:     a2664e70597e36d3e50f9f92ea3260439ae20478
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 12 20:48:47 2022 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Tue Jul 12 21:01:29 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a2664e70

dev-ruby/bcrypt-ruby: drop 3.1.16, 3.1.16-r1, 3.1.16-r2

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/bcrypt-ruby/Manifest                     |  1 -
 dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16-r1.ebuild | 52 --------------------
 dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16-r2.ebuild | 52 --------------------
 dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16.ebuild    | 59 -----------------------
 4 files changed, 164 deletions(-)

diff --git a/dev-ruby/bcrypt-ruby/Manifest b/dev-ruby/bcrypt-ruby/Manifest
index d345254a703b..bd4834a13a1e 100644
--- a/dev-ruby/bcrypt-ruby/Manifest
+++ b/dev-ruby/bcrypt-ruby/Manifest
@@ -1,3 +1,2 @@
-DIST bcrypt-3.1.16.gem 54272 BLAKE2B df8e1169df3a67f3eedd90b4fe04224266cd41d1a0dd2866b06372805b5b00aa028c3bb077078ffde3c89a9052497016dc3fe812075d8b6f57d6dd951a6aa806 SHA512 655483d73347c20f3b04a24d625cde05fd8e1da6f022363fbb2df828aea0623cb5b4981d97791301dcd83edc2719a2238d8d377af1558ca2ce4b3c8ade9bd343
 DIST bcrypt-3.1.17.gem 55808 BLAKE2B e2e3d6ebeaf3d52fa69eb2da340c9558c09f526cc29a1230e2f439f32952a916ba6c2336a134ed0a2ca5210dbb8d2f0818c9ec56283e20f25cb9f891b07bdc60 SHA512 527103e758387031cd6153f5806eb161642547e89dda359929d88b0cc676175e4b3c63905fc8ed724914d2f8b152ecc7f6e7cf5d0c66b7c6fbf7b899bade16a7
 DIST bcrypt-3.1.18.gem 55808 BLAKE2B 03e4082f451b8410ae88c1d920625cf3249094ba2d6fc04429d5f9cd60d7e29fa1c3170e2409ba16fa8fd8c341c7471047a382ee89cb2b04dab9bbdaadc3554a SHA512 b0b44f49ac2ef7a6a75a8949943291b7d37fc80be6a4dbbbcbbf117feaa4ff09b0670c14879c358fc2dadd22866cad6e26d07cfdcbb9423d0c52a6f54ae3f8f5

diff --git a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16-r1.ebuild b/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16-r1.ebuild
deleted file mode 100644
index 079fc8ba9897..000000000000
--- a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16-r1.ebuild
+++ /dev/null
@@ -1,52 +0,0 @@
-# Copyright 1999-2021 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-USE_RUBY="ruby25 ruby26 ruby27"
-
-RUBY_FAKEGEM_RECIPE_TEST="rspec3"
-
-RUBY_FAKEGEM_TASK_DOC=""
-RUBY_FAKEGEM_EXTRADOC="CHANGELOG README.md"
-
-RUBY_FAKEGEM_NAME="bcrypt"
-
-RUBY_FAKEGEM_EXTENSIONS=(ext/mri/extconf.rb)
-
-inherit multilib ruby-fakegem
-
-DESCRIPTION="An easy way to keep your users' passwords secure"
-HOMEPAGE="https://github.com/codahale/bcrypt-ruby"
-LICENSE="MIT"
-
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
-SLOT="0"
-IUSE=""
-
-all_ruby_prepare() {
-	rm Gemfile || die
-	sed -i -e '/git ls-files/d' bcrypt.gemspec || die
-}
-
-each_ruby_install() {
-		each_fakegem_install
-
-		# bcrypt was called bcrypt-ruby before, so add a spec file that
-		# simply loads bcrypt to make sure that old projects load correctly
-		# we don't even need to create a file to load this: the `require
-		# bcrypt` was already part of bcrypt-ruby requirements.
-		cat - <<EOF > "${T}/bcrypt-ruby.gemspec"
-Gem::Specification.new do |s|
-	s.name = "bcrypt-ruby"
-	s.version = "${RUBY_FAKEGEM_VERSION}"
-	s.summary = "Fake gem to load bcrypt"
-	s.homepage = "${HOMEPAGE}"
-	s.specification_version = 3
-	s.add_runtime_dependency("${RUBY_FAKEGEM_NAME}", ["= ${RUBY_FAKEGEM_VERSION}"])
-end
-EOF
-		RUBY_FAKEGEM_NAME=bcrypt-ruby \
-				RUBY_FAKEGEM_GEMSPEC="${T}/bcrypt-ruby.gemspec" \
-				ruby_fakegem_install_gemspec
-}

diff --git a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16-r2.ebuild b/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16-r2.ebuild
deleted file mode 100644
index c96faac55005..000000000000
--- a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16-r2.ebuild
+++ /dev/null
@@ -1,52 +0,0 @@
-# Copyright 1999-2021 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-USE_RUBY="ruby26 ruby27 ruby30"
-
-RUBY_FAKEGEM_RECIPE_TEST="rspec3"
-
-RUBY_FAKEGEM_TASK_DOC=""
-RUBY_FAKEGEM_EXTRADOC="CHANGELOG README.md"
-
-RUBY_FAKEGEM_NAME="bcrypt"
-
-RUBY_FAKEGEM_EXTENSIONS=(ext/mri/extconf.rb)
-
-inherit multilib ruby-fakegem
-
-DESCRIPTION="An easy way to keep your users' passwords secure"
-HOMEPAGE="https://github.com/codahale/bcrypt-ruby"
-LICENSE="MIT"
-
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
-SLOT="0"
-IUSE=""
-
-all_ruby_prepare() {
-	rm Gemfile || die
-	sed -i -e '/git ls-files/d' bcrypt.gemspec || die
-}
-
-each_ruby_install() {
-		each_fakegem_install
-
-		# bcrypt was called bcrypt-ruby before, so add a spec file that
-		# simply loads bcrypt to make sure that old projects load correctly
-		# we don't even need to create a file to load this: the `require
-		# bcrypt` was already part of bcrypt-ruby requirements.
-		cat - <<EOF > "${T}/bcrypt-ruby.gemspec"
-Gem::Specification.new do |s|
-	s.name = "bcrypt-ruby"
-	s.version = "${RUBY_FAKEGEM_VERSION}"
-	s.summary = "Fake gem to load bcrypt"
-	s.homepage = "${HOMEPAGE}"
-	s.specification_version = 3
-	s.add_runtime_dependency("${RUBY_FAKEGEM_NAME}", ["= ${RUBY_FAKEGEM_VERSION}"])
-end
-EOF
-		RUBY_FAKEGEM_NAME=bcrypt-ruby \
-				RUBY_FAKEGEM_GEMSPEC="${T}/bcrypt-ruby.gemspec" \
-				ruby_fakegem_install_gemspec
-}

diff --git a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16.ebuild b/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16.ebuild
deleted file mode 100644
index 17bacd6c56df..000000000000
--- a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.16.ebuild
+++ /dev/null
@@ -1,59 +0,0 @@
-# Copyright 1999-2021 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-USE_RUBY="ruby25 ruby26 ruby27"
-
-RUBY_FAKEGEM_RECIPE_TEST="rspec3"
-
-RUBY_FAKEGEM_TASK_DOC=""
-RUBY_FAKEGEM_EXTRADOC="CHANGELOG README.md"
-
-RUBY_FAKEGEM_NAME="bcrypt"
-
-inherit multilib ruby-fakegem
-
-DESCRIPTION="An easy way to keep your users' passwords secure"
-HOMEPAGE="https://github.com/codahale/bcrypt-ruby"
-LICENSE="MIT"
-
-KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
-SLOT="0"
-IUSE=""
-
-all_ruby_prepare() {
-	rm Gemfile || die
-	sed -i -e '/git ls-files/d' bcrypt.gemspec || die
-}
-
-each_ruby_configure() {
-	${RUBY} -Cext/mri extconf.rb || die
-}
-
-each_ruby_compile() {
-	emake -Cext/mri V=1
-	cp ext/mri/*$(get_modname) lib/ || die
-}
-
-each_ruby_install() {
-		each_fakegem_install
-
-		# bcrypt was called bcrypt-ruby before, so add a spec file that
-		# simply loads bcrypt to make sure that old projects load correctly
-		# we don't even need to create a file to load this: the `require
-		# bcrypt` was already part of bcrypt-ruby requirements.
-		cat - <<EOF > "${T}/bcrypt-ruby.gemspec"
-Gem::Specification.new do |s|
-	s.name = "bcrypt-ruby"
-	s.version = "${RUBY_FAKEGEM_VERSION}"
-	s.summary = "Fake gem to load bcrypt"
-	s.homepage = "${HOMEPAGE}"
-	s.specification_version = 3
-	s.add_runtime_dependency("${RUBY_FAKEGEM_NAME}", ["= ${RUBY_FAKEGEM_VERSION}"])
-end
-EOF
-		RUBY_FAKEGEM_NAME=bcrypt-ruby \
-				RUBY_FAKEGEM_GEMSPEC="${T}/bcrypt-ruby.gemspec" \
-				ruby_fakegem_install_gemspec
-}

next             reply	other threads:[~2022-07-12 21:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 21:01 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-01  8:20 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/bcrypt-ruby/ Hans de Graaff
2024-11-08 14:22 Hans de Graaff
2024-10-06  9:32 Hans de Graaff
2023-12-31 19:49 Hans de Graaff
2023-11-18  8:09 Hans de Graaff
2023-11-18  8:09 Hans de Graaff
2023-06-23  4:27 Hans de Graaff
2023-06-23  4:27 Hans de Graaff
2023-04-01 20:09 Sam James
2023-03-28 16:10 Sam James
2022-05-17  5:32 Hans de Graaff
2022-05-17  5:32 Hans de Graaff
2022-05-07  6:34 Hans de Graaff
2022-03-15  6:59 Hans de Graaff
2021-11-13  5:24 Hans de Graaff
2021-11-08  2:51 Yixun Lan
2021-10-31  5:57 Hans de Graaff
2021-06-30  6:56 Hans de Graaff
2021-06-30  6:56 Hans de Graaff
2020-09-06  6:48 Hans de Graaff
2020-09-04  5:06 Hans de Graaff
2020-08-23  6:24 Hans de Graaff
2020-07-22  4:30 Hans de Graaff
2020-07-22  4:30 Hans de Graaff
2020-04-20 17:05 Sergei Trofimovich
2020-04-19 23:55 Sergei Trofimovich
2020-04-19 23:55 Sergei Trofimovich
2020-03-09  7:06 Hans de Graaff
2019-06-01  5:19 Hans de Graaff
2019-06-01  5:19 Hans de Graaff
2019-02-03 10:49 Hans de Graaff
2018-05-17  4:57 Hans de Graaff
2018-05-09  4:56 Hans de Graaff
2017-12-25  7:58 Hans de Graaff
2017-08-27  6:18 Hans de Graaff
2017-05-13  6:33 Hans de Graaff
2016-07-14  5:52 Hans de Graaff
2016-06-08 18:00 Hans de Graaff
2016-04-03 21:44 Manuel Rüger
2016-03-06  6:22 Hans de Graaff

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:d345254a703 dfblob:bd4834a13a1 dfblob:079fc8ba989
dfblob:c96faac5500 dfblob:17bacd6c56d )
 OR (
bs:"[gentoo-commits] repo/gentoo:master commit in: dev-ruby/bcrypt-ruby/" )
	(help)

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=1657659689.a2664e70597e36d3e50f9f92ea3260439ae20478.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