From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] dev/graaff:master commit in: dev-ruby/scrypt/
Date: Sun, 14 Feb 2016 19:29:28 +0000 (UTC) [thread overview]
Message-ID: <1455474654.d0192748f21f2b3203a636c55df580d1c5bb9715.graaff@gentoo> (raw)
commit: d0192748f21f2b3203a636c55df580d1c5bb9715
Author: Hans de Graaff <hans <AT> degraaff <DOT> org>
AuthorDate: Sun Feb 14 18:30:54 2016 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Feb 14 18:30:54 2016 +0000
URL: https://gitweb.gentoo.org/dev/graaff.git/commit/?id=d0192748
dev-ruby/scrypt: cleanup
Package-Manager: portage-2.2.26
dev-ruby/scrypt/Manifest | 1 -
dev-ruby/scrypt/scrypt-2.0.0.ebuild | 37 -------------------------------------
2 files changed, 38 deletions(-)
diff --git a/dev-ruby/scrypt/Manifest b/dev-ruby/scrypt/Manifest
index 54d7f86..ac89483 100644
--- a/dev-ruby/scrypt/Manifest
+++ b/dev-ruby/scrypt/Manifest
@@ -1,2 +1 @@
-DIST scrypt-2.0.0.gem 23552 SHA256 34cf4f10e0fa4b03b6722e3987a9907fd89a83293dabcc5333541349a2da17ea SHA512 d8543d263d2109f5428688d4589a643ef62a458c5c3cc683cff64c1d98c316e4232977757e52a75247da2be4d7e7d3bedc3d1ceada286e03e064f0198c043606 WHIRLPOOL 7ccd368db889fd58a73eb2b18cfb747d83828885b965eeca6bbe118fb7d108b00151632019ff7ca35089ac56098f457c370e25d85174a51921793038f9e978b3
DIST scrypt-2.0.2.gem 28160 SHA256 ff879435a7ec15d78679f0d228ab976bb2633cc78faa25ab57f9538c4e8a2aaf SHA512 7c82bba94eb18a2340964c2fbf1f6ca2c4af310baa318b50e3932d8bd72a60fe90c5a85d09ce3157ae3589964da8f93742fd7ae5e42e571e1d5848af6164c928 WHIRLPOOL ada6f8ef98f16c5d05b3f808a5c6e9683bbcb48387be0d12cbbf92cb7eecb57366ed2a5e6df165facb61e51df35e22cde1782c39e9f6695df73f233ade2b442d
diff --git a/dev-ruby/scrypt/scrypt-2.0.0.ebuild b/dev-ruby/scrypt/scrypt-2.0.0.ebuild
deleted file mode 100644
index ec08cf8..0000000
--- a/dev-ruby/scrypt/scrypt-2.0.0.ebuild
+++ /dev/null
@@ -1,37 +0,0 @@
-# Copyright 1999-2015 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-# $Header: $
-
-EAPI=5
-USE_RUBY="ruby19 ruby20 ruby21"
-
-RUBY_FAKEGEM_RECIPE_DOC="rdoc"
-RUBY_FAKEGEM_EXTRADOC="README.md"
-
-RUBY_FAKEGEM_RECIPE_TEST="rspec3"
-
-RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
-
-inherit ruby-fakegem
-
-DESCRIPTION="Scrypt password hashing algorithm"
-HOMEPAGE="https://github.com/pbhogan/scrypt"
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="~amd64"
-IUSE=""
-
-ruby_add_bdepend ">=dev-ruby/ffi-compiler-0.0.2"
-
-all_ruby_prepare() {
- # In Gentoo ffi-compiler can be a built-time only dependency.
- sed -i -e '/ffi-compiler/d' ${RUBY_FAKEGEM_GEMSPEC} || die
-}
-
-each_ruby_compile() {
- # This task ignores CFLAGS and LDFLAGS and hardcodes sse and sse2
- # support. This should be fixed before moving it to the gentoo tree.
- ${RUBY} -Cext/scrypt -S rake || die
- cp ext/scrypt/*/libscrypt_ext.so lib/
-}
next reply other threads:[~2016-02-14 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 19:29 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-10 6:25 [gentoo-commits] dev/graaff:master commit in: dev-ruby/scrypt/ Hans de Graaff
2016-02-14 19:29 Hans de Graaff
2015-06-12 5:05 Hans de Graaff
2015-01-03 6:59 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=1455474654.d0192748f21f2b3203a636c55df580d1c5bb9715.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