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/bcrypt-ruby/
Date: Sat,  1 Apr 2023 20:09:10 +0000 (UTC)	[thread overview]
Message-ID: <1680379718.92c55db7881dcdc2c010461663d3740200f5272b.sam@gentoo> (raw)

commit:     92c55db7881dcdc2c010461663d3740200f5272b
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 31 23:16:55 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Apr  1 20:08:38 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=92c55db7

dev-ruby/bcrypt-ruby: enable ruby32, fix indentation

- Enable ruby32
- Use <<- instead of << to strip whitespace which lets us have
the necessary indentation without double-indenting/not-indenting-at-all
(this preserves the indentation in the gemspec)
- Add missing die in heredoc

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

 dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.18.ebuild | 44 ++++++++++++--------------
 1 file changed, 21 insertions(+), 23 deletions(-)

diff --git a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.18.ebuild b/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.18.ebuild
index c7938cd7693d..58da5a7621b9 100644
--- a/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.18.ebuild
+++ b/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.18.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=8
 
-USE_RUBY="ruby26 ruby27 ruby30 ruby31"
+USE_RUBY="ruby27 ruby30 ruby31 ruby32"
 
 RUBY_FAKEGEM_RECIPE_TEST="rspec3"
 
@@ -18,11 +18,10 @@ inherit 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"
+LICENSE="MIT"
 SLOT="0"
-IUSE=""
+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"
 
 all_ruby_prepare() {
 	rm Gemfile || die
@@ -30,23 +29,22 @@ all_ruby_prepare() {
 }
 
 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
+	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" || die
+	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
 }


             reply	other threads:[~2023-04-01 20:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 20:09 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-08 14:22 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/bcrypt-ruby/ 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-03-28 16:10 Sam James
2022-07-12 21:01 Hans de Graaff
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

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=1680379718.92c55db7881dcdc2c010461663d3740200f5272b.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