From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/bcrypt_pbkdf/
Date: Sun, 9 Feb 2020 15:07:46 +0000 (UTC) [thread overview]
Message-ID: <1581260858.86d2e776d55126b897f49bd6dc224e56101cf7cb.graaff@gentoo> (raw)
commit: 86d2e776d55126b897f49bd6dc224e56101cf7cb
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 9 14:59:17 2020 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Feb 9 15:07:38 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=86d2e776
dev-ruby/bcrypt_pbkdf: add ruby27
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/bcrypt_pbkdf/bcrypt_pbkdf-1.0.1.ebuild | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/dev-ruby/bcrypt_pbkdf/bcrypt_pbkdf-1.0.1.ebuild b/dev-ruby/bcrypt_pbkdf/bcrypt_pbkdf-1.0.1.ebuild
index 54cd5f62f5a..25f0fe94d72 100644
--- a/dev-ruby/bcrypt_pbkdf/bcrypt_pbkdf-1.0.1.ebuild
+++ b/dev-ruby/bcrypt_pbkdf/bcrypt_pbkdf-1.0.1.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2019 Gentoo Authors
+# Copyright 1999-2020 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=5
-USE_RUBY="ruby23 ruby24 ruby25 ruby26"
+USE_RUBY="ruby24 ruby25 ruby26 ruby27"
RUBY_FAKEGEM_RECIPE_DOC="rdoc"
RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md"
@@ -25,7 +25,9 @@ all_ruby_prepare() {
sed -i -e '/rbnacl\/libsodium/ s:^:#:' test/bcrypt_pnkdf/engine_test.rb || die
# Avoid unneeded rake-compiler dependency
- sed -i -e '/extensiontask/ s:^:#:' -e '/ExtensionTask/,/^end/ s:^:#:' Rakefile || die
+ sed -e '/extensiontask/ s:^:#:' -e '/ExtensionTask/,/^end/ s:^:#:' \
+ -e '/bundler/ s:^:#:' \
+ -i Rakefile || die
}
each_ruby_configure() {
next reply other threads:[~2020-02-09 15:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 15:07 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-30 7:58 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/bcrypt_pbkdf/ Hans de Graaff
2024-12-30 7:58 Hans de Graaff
2024-09-12 16:16 Jakov Smolić
2024-09-11 14:15 Sam James
2024-09-09 11:11 Sam James
2024-09-09 11:11 Sam James
2024-05-20 7:07 Hans de Graaff
2024-01-10 7:44 Hans de Graaff
2023-07-08 8:59 Hans de Graaff
2023-04-17 9:46 Sam James
2023-04-17 9:35 Sam James
2023-04-17 9:35 Sam James
2023-04-17 9:35 Sam James
2023-03-13 7:14 Hans de Graaff
2022-08-17 15:39 Sam James
2022-03-31 5:39 Hans de Graaff
2021-09-25 8:49 Hans de Graaff
2021-09-25 5:18 Agostino Sarubbo
2021-09-22 6:58 Agostino Sarubbo
2021-09-20 6:26 Agostino Sarubbo
2021-09-19 21:35 Agostino Sarubbo
2021-07-06 7:49 Hans de Graaff
2021-06-30 6:56 Hans de Graaff
2021-06-30 6:56 Hans de Graaff
2021-01-06 6:21 Hans de Graaff
2019-04-06 5:56 Hans de Graaff
2019-01-19 14:48 Hans de Graaff
2018-11-26 15:44 Rick Farina
2018-07-30 19:44 Hans de Graaff
2018-06-27 22:15 Sergei Trofimovich
2018-06-26 2:04 Aaron Bauman
2018-05-03 4:42 Hans de Graaff
2018-04-08 9:13 Sergei Trofimovich
2018-04-02 6:55 Hans de Graaff
2018-03-13 22:39 Sergei Trofimovich
2018-02-16 10:31 Hans de Graaff
2018-02-11 21:56 Thomas Deutschmann
2017-06-10 7:31 Hans de Graaff
2017-02-27 6:52 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=1581260858.86d2e776d55126b897f49bd6dc224e56101cf7cb.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