From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/yajl-ruby/
Date: Wed, 8 Nov 2017 06:37:05 +0000 (UTC) [thread overview]
Message-ID: <1510123003.e5171d48f94f79e2a8c7eecd21a5917416eb9d9a.graaff@gentoo> (raw)
commit: e5171d48f94f79e2a8c7eecd21a5917416eb9d9a
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 8 06:36:26 2017 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed Nov 8 06:36:43 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e5171d48
dev-ruby/yajl-ruby: add 1.3.1, fixing bug 636474
Bug: https://bugs.gentoo.org/636474
Package-Manager: Portage-2.3.8, Repoman-2.3.3
dev-ruby/yajl-ruby/Manifest | 1 +
dev-ruby/yajl-ruby/yajl-ruby-1.3.1.ebuild | 45 +++++++++++++++++++++++++++++++
2 files changed, 46 insertions(+)
diff --git a/dev-ruby/yajl-ruby/Manifest b/dev-ruby/yajl-ruby/Manifest
index 98fac4859e3..f27d973ee54 100644
--- a/dev-ruby/yajl-ruby/Manifest
+++ b/dev-ruby/yajl-ruby/Manifest
@@ -1,2 +1,3 @@
DIST yajl-ruby-1.1.0.gem 557056 SHA256 95b85940c96c0745e780f363170b8bd1b7b66d36073a061b1461b1788834446a SHA512 bde81b5fbe467c6403d27b49075822ff07b5cf356c05f711757fea5162543af36846f1f1da36acd5da359133f05e2cb3186215dc5597f3255da74c76cc8bf3ec WHIRLPOOL baa8f6ec2bfe70cd8f3441c971b2854a99b9f132eb2cae22f9fe6a9de7c7ccbf84f0f3ec982296d4cbc998051529b464aaf16b268049193aa4170ec7ec1ca11b
DIST yajl-ruby-1.3.0.gem 550912 SHA256 f1941b3606aa8da0800ab0a5560929454a1ba9c7ec41cb5a2905eabb2f155069 SHA512 351e46fb7037541096172bac5c3dcadaa6ac9650ac6aae46de2b4ba31b82427f596bade2b233d0d8e916927800e83b7930b5ceeb9d7340edd02c323f9c0b3116 WHIRLPOOL 8de8b6575f3972dbb2503315d33f5701f6141b0ce11f9f3b027a7c15ab257823e772d14400dc3db94b41135e90b25c89a89931fb2670a7e0de72a0ee40d885dc
+DIST yajl-ruby-1.3.1.gem 550912 SHA256 60bc04e0e58ce689a4f37787ba152b037a960da48f8b229a072929e8129bc4e6 SHA512 f18b47f1fd0b039bfec01db0ee298296199fbf91b22a00042e1220a1d8471f72424c082b696829e48ce7dee7514510dd731c2bc36fe29bd08ba7246c820621f4 WHIRLPOOL 369462f5104b826f9160215a06050bdc53f61ef937a8461d8e1a11b62d68267fec3a0cae087cf4be6f161e76d1b92c077f9d861c3ce027927308bbb6afab2709
diff --git a/dev-ruby/yajl-ruby/yajl-ruby-1.3.1.ebuild b/dev-ruby/yajl-ruby/yajl-ruby-1.3.1.ebuild
new file mode 100644
index 00000000000..b8ecc24eded
--- /dev/null
+++ b/dev-ruby/yajl-ruby/yajl-ruby-1.3.1.ebuild
@@ -0,0 +1,45 @@
+# Copyright 1999-2017 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+
+USE_RUBY="ruby22 ruby23 ruby24"
+
+RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md"
+
+RUBY_FAKEGEM_RECIPE_TEST="rspec3"
+
+RUBY_FAKEGEM_TASK_DOC=""
+
+inherit multilib ruby-fakegem
+
+DESCRIPTION="Ruby C bindings to the Yajl JSON stream-based parser library"
+HOMEPAGE="https://github.com/brianmario/yajl-ruby"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+IUSE=""
+
+RDEPEND="${RDEPEND} dev-libs/yajl"
+DEPEND="${DEPEND} dev-libs/yajl"
+
+each_ruby_prepare() {
+ # Make sure the right ruby interpreter is used
+ sed -e '/capture/ s:ruby:'${RUBY}':' -i spec/parsing/large_number_spec.rb || die
+}
+
+each_ruby_configure() {
+ ${RUBY} -Cext/yajl extconf.rb || die "extconf.rb failed"
+}
+
+each_ruby_compile() {
+ emake -Cext/yajl CFLAGS="${CFLAGS} -fPIC" archflag="${LDFLAGS}" V=1
+ cp ext/yajl/yajl$(get_modname) lib/yajl/ || die
+}
+
+each_ruby_test() {
+ # Set RUBYLIB to pass search path on to additional interpreters that
+ # are started.
+ RUBYLIB=lib ruby-ng_rspec || die
+}
next reply other threads:[~2017-11-08 6:37 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 6:37 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-31 8:05 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/yajl-ruby/ Hans de Graaff
2023-03-28 19:24 Sam James
2023-03-28 19:24 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:05 Sam James
2023-03-10 20:29 Hans de Graaff
2022-05-27 5:39 Hans de Graaff
2022-04-15 14:00 Hans de Graaff
2022-04-13 9:32 Jakov Smolić
2022-04-11 6:50 Agostino Sarubbo
2022-04-11 6:35 Jakov Smolić
2022-04-10 17:54 Arthur Zamarin
2022-04-10 17:54 Arthur Zamarin
2022-04-10 17:51 Arthur Zamarin
2022-04-10 17:47 Arthur Zamarin
2022-04-06 5:48 Hans de Graaff
2021-07-07 8:31 Hans de Graaff
2021-01-06 18:32 Fabian Groffen
2020-12-17 7:51 Sam James
2020-11-06 3:21 Sam James
2020-07-19 6:15 Hans de Graaff
2020-06-19 6:40 Sergei Trofimovich
2020-06-15 15:16 Agostino Sarubbo
2020-06-15 15:12 Agostino Sarubbo
2020-06-15 15:03 Agostino Sarubbo
2020-06-14 20:19 Sergei Trofimovich
2020-06-14 20:08 Sergei Trofimovich
2020-01-19 6:52 Hans de Graaff
2019-11-02 5:55 Hans de Graaff
2019-04-27 15:20 Sergei Trofimovich
2019-01-12 7:42 Hans de Graaff
2018-07-28 4:47 Hans de Graaff
2018-07-20 5:33 Hans de Graaff
2018-07-13 19:04 Hans de Graaff
2018-07-13 18:46 Sergei Trofimovich
2018-07-11 23:55 Mikle Kolyada
2018-04-30 5:15 Hans de Graaff
2018-04-28 7:23 Mikle Kolyada
2018-04-11 20:43 Thomas Deutschmann
2018-04-06 22:44 Sergei Trofimovich
2018-04-06 17:13 Tobias Klausmann
2018-04-06 14:26 Aaron Bauman
2018-04-06 4:54 Hans de Graaff
2017-12-22 6:00 Hans de Graaff
2017-12-21 19:28 Markus Meier
2017-12-06 22:44 Sergei Trofimovich
2017-10-22 21:34 Thomas Deutschmann
2017-10-22 9:21 Hans de Graaff
2017-10-22 9:21 Hans de Graaff
2017-10-14 22:00 Sergei Trofimovich
2017-09-24 16:16 Sergei Trofimovich
2017-08-23 21:43 Sergei Trofimovich
2017-08-23 6:14 Hans de Graaff
2017-06-05 8:44 Hans de Graaff
2016-12-11 7:26 Hans de Graaff
2016-11-02 5:52 Hans de Graaff
2016-07-21 19:39 Hans de Graaff
2016-03-28 10:21 Hans de Graaff
2016-03-06 18:25 Manuel Rüger
2016-03-06 18:25 Manuel Rüger
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=1510123003.e5171d48f94f79e2a8c7eecd21a5917416eb9d9a.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