Сравнение bcrypt-ruby-3.1.18 с bcrypt-ruby-3.1.19
| /usr/portage/dev-ruby/bcrypt-ruby/bcrypt-ruby-3.1.19.ebuild 2023-10-09 14:52:30.424368374 +0300 | ||
|---|---|---|
| 3 | 3 | |
| 4 | 4 |
EAPI=8 |
| 5 | 5 | |
| 6 |
USE_RUBY="ruby27 ruby30 ruby31 ruby32" |
|
| 6 |
USE_RUBY="ruby30 ruby31 ruby32" |
|
| 7 | 7 | |
| 8 | 8 |
RUBY_FAKEGEM_RECIPE_TEST="rspec3" |
| 9 | 9 | |
| ... | ... | |
| 17 | 17 |
inherit ruby-fakegem |
| 18 | 18 | |
| 19 | 19 |
DESCRIPTION="An easy way to keep your users' passwords secure" |
| 20 |
HOMEPAGE="https://github.com/codahale/bcrypt-ruby" |
|
| 20 |
HOMEPAGE="https://github.com/bcrypt-ruby/bcrypt-ruby" |
|
| 21 | 21 | |
| 22 | 22 |
LICENSE="MIT" |
| 23 | 23 |
SLOT="0" |
| ... | ... | |
| 27 | 27 |
rm Gemfile || die |
| 28 | 28 |
sed -i -e 's/git ls-files/find */' bcrypt.gemspec || die |
| 29 | 29 |
} |
| 30 | ||
| 31 |
each_ruby_install() {
|
|
| 32 |
each_fakegem_install |
|
| 33 | ||
| 34 |
# bcrypt was called bcrypt-ruby before, so add a spec file that |
|
| 35 |
# simply loads bcrypt to make sure that old projects load correctly |
|
| 36 |
# we don't even need to create a file to load this: the `require |
|
| 37 |
# bcrypt` was already part of bcrypt-ruby requirements. |
|
| 38 |
cat <<-EOF > "${T}/bcrypt-ruby.gemspec" || die
|
|
| 39 |
Gem::Specification.new do |s| |
|
| 40 |
s.name = "bcrypt-ruby" |
|
| 41 |
s.version = "${RUBY_FAKEGEM_VERSION}"
|
|
| 42 |
s.summary = "Fake gem to load bcrypt" |
|
| 43 |
s.homepage = "${HOMEPAGE}"
|
|
| 44 |
s.specification_version = 3 |
|
| 45 |
s.add_runtime_dependency("${RUBY_FAKEGEM_NAME}", ["= ${RUBY_FAKEGEM_VERSION}"])
|
|
| 46 |
end |
|
| 47 |
EOF |
|
| 48 | ||
| 49 |
RUBY_FAKEGEM_NAME=bcrypt-ruby RUBY_FAKEGEM_GEMSPEC="${T}/bcrypt-ruby.gemspec" ruby_fakegem_install_gemspec
|
|
| 50 |
} |
|