From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/hashery/
Date: Mon, 2 May 2016 05:26:11 +0000 (UTC) [thread overview]
Message-ID: <1462166756.4d969b310037a11b12b127938324fac48adc9046.graaff@gentoo> (raw)
commit: 4d969b310037a11b12b127938324fac48adc9046
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon May 2 05:18:37 2016 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon May 2 05:25:56 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d969b31
dev-ruby/hashery: add 2.1.2
Package-Manager: portage-2.2.26
dev-ruby/hashery/Manifest | 1 +
dev-ruby/hashery/hashery-2.1.2.ebuild | 31 +++++++++++++++++++++++++++++++
2 files changed, 32 insertions(+)
diff --git a/dev-ruby/hashery/Manifest b/dev-ruby/hashery/Manifest
index 959f2b0..da4f2a8 100644
--- a/dev-ruby/hashery/Manifest
+++ b/dev-ruby/hashery/Manifest
@@ -1 +1,2 @@
DIST hashery-2.1.1.gem 43008 SHA256 8f94ee21ba35f970d188491318f9b79ff7288e517301700e4d342ba9255d5c75 SHA512 f0fb1a0ca41264170bfeb970a2df5920109ed273f4f4617cfbde92e889ce6b5ec34e61be442182ddfca86efa13df3aab537bbc40d2c1e7791b74a9e5b4e0ca24 WHIRLPOOL 3b7e2e5b44ba917feec676c7548bdfca63c93f621eb296e36c6fcb87f3b1a5fedf0ce4335bac8cf369f364a980ec3c39617d4c3b5fc6b6aecc3f6e77c57e489b
+DIST hashery-2.1.2.gem 43008 SHA256 d239cc2310401903f6b79d458c2bbef5bf74c46f3f974ae9c1061fb74a404862 SHA512 953fb7024aeeff8720c14880f8cbf0ee03cc09624ba33152215439a2e252cea22167258e8e8c1cb023129a51cd95b2d9d33ca794a6b38560a8eb1e0fe44f290b WHIRLPOOL 5bb4f38614665c8970c9f5c9cc3ed1ac5b982d2003343b518890ca22da6869071ec257179b71680bef006d7ad639222b58f9c8e6a089ea79ab1e69278ba040e8
diff --git a/dev-ruby/hashery/hashery-2.1.2.ebuild b/dev-ruby/hashery/hashery-2.1.2.ebuild
new file mode 100644
index 0000000..859e0a1
--- /dev/null
+++ b/dev-ruby/hashery/hashery-2.1.2.ebuild
@@ -0,0 +1,31 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=5
+USE_RUBY="ruby20 ruby21 ruby22"
+
+RUBY_FAKEGEM_TASK_TEST=""
+RUBY_FAKEGEM_RECIPE_DOC="yard"
+RUBY_FAKEGEM_EXTRADOC="README.md"
+
+inherit ruby-fakegem
+
+DESCRIPTION="The Hashery is a tight collection of Hash-like classes"
+HOMEPAGE="https://rubyworks.github.com/hashery"
+
+LICENSE="BSD-2"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
+IUSE=""
+
+ruby_add_bdepend "test? (
+ dev-ruby/lemon
+ dev-ruby/qed
+ dev-ruby/rubytest
+ dev-ruby/rubytest-cli )"
+
+each_ruby_test() {
+ ${RUBY} -S qed || die 'tests failed'
+ ${RUBY} -S rubytest -Ilib -Itest test/ || die 'tests failed'
+}
next reply other threads:[~2016-05-02 5:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 5:26 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-24 4:59 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/hashery/ Hans de Graaff
2017-01-22 1:34 Manuel Rüger
2018-03-24 8:35 Hans de Graaff
2018-04-15 5:23 Hans de Graaff
2019-05-08 19:59 Hans de Graaff
2020-02-22 10:22 Hans de Graaff
2021-10-23 6:55 Hans de Graaff
2021-11-17 6:37 Hans de Graaff
2022-06-18 5:48 Hans de Graaff
2023-06-29 20:13 Hans de Graaff
2024-02-14 6:49 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=1462166756.4d969b310037a11b12b127938324fac48adc9046.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