From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/pg/
Date: Mon, 18 Jul 2016 06:49:00 +0000 (UTC) [thread overview]
Message-ID: <1468824488.5b2d958c16e9c079253c788869f419b04ce4d00b.graaff@gentoo> (raw)
commit: 5b2d958c16e9c079253c788869f419b04ce4d00b
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 18 06:33:42 2016 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Jul 18 06:48:08 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5b2d958c
dev-ruby/pg: add ruby23 revision
Package-Manager: portage-2.2.28
dev-ruby/pg/pg-0.18.4-r1.ebuild | 62 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 62 insertions(+)
diff --git a/dev-ruby/pg/pg-0.18.4-r1.ebuild b/dev-ruby/pg/pg-0.18.4-r1.ebuild
new file mode 100644
index 0000000..d5c133c
--- /dev/null
+++ b/dev-ruby/pg/pg-0.18.4-r1.ebuild
@@ -0,0 +1,62 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=5
+USE_RUBY="ruby20 ruby21 ruby22 ruby23"
+
+RUBY_FAKEGEM_RECIPE_TEST="rspec3"
+
+RUBY_FAKEGEM_TASK_DOC="docs"
+RUBY_FAKEGEM_DOCDIR="doc"
+RUBY_FAKEGEM_EXTRADOC="ChangeLog Contributors.rdoc README.rdoc History.rdoc"
+
+inherit multilib ruby-fakegem
+
+DESCRIPTION="Ruby extension library providing an API to PostgreSQL"
+HOMEPAGE="https://bitbucket.org/ged/ruby-pg/"
+
+LICENSE="|| ( GPL-2 Ruby )"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ppc64 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+IUSE=""
+
+RDEPEND+=" dev-db/postgresql:*"
+DEPEND+=" dev-db/postgresql
+ test? ( >=dev-db/postgresql-9.4[server,threads] )"
+
+ruby_add_bdepend "
+ doc? (
+ dev-ruby/hoe
+ || ( >=dev-ruby/yard-0.6.1 dev-ruby/rdoc ) )"
+
+all_ruby_prepare() {
+ # hack the Rakefile to make it sure that it doesn't load
+ # rake-compiler (so that we don't have to depend on it and it
+ # actually works when building with USE=doc).
+ sed -i \
+ -e '/Rakefile.cross/s:^:#:' \
+ -e '/ExtensionTask/,/^end$/ s:^:#:' \
+ Rakefile || die
+}
+
+each_ruby_configure() {
+ ${RUBY} -C ext extconf.rb || die "extconf.rb failed"
+}
+
+each_ruby_compile() {
+ emake V=1 -C ext CFLAGS="${CFLAGS} -fPIC" archflag="${LDFLAGS}"
+ cp ext/*$(get_libname) lib || die
+}
+
+each_ruby_test() {
+ if [[ "${EUID}" -ne "0" ]]; then
+ # Make the rspec call explicit, this way we don't have to depend
+ # on rake-compiler (nor rubygems) _and_ we don't have to rebuild
+ # the whole extension from scratch.
+ RSPEC_VERSION=3 ruby-ng_rspec
+ else
+ ewarn "The userpriv feature must be enabled to run tests."
+ eerror "Testsuite will not be run."
+ fi
+}
next reply other threads:[~2016-07-18 6:49 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 6:49 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-04 16:33 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/pg/ Hans de Graaff
2024-11-04 16:33 Hans de Graaff
2024-10-30 14:41 Sam James
2024-10-30 6:17 Hans de Graaff
2024-10-24 12:30 Arthur Zamarin
2024-10-24 12:30 Arthur Zamarin
2024-09-07 8:29 Hans de Graaff
2024-08-21 9:19 Joonas Niilola
2024-08-18 7:25 Hans de Graaff
2024-06-02 6:41 Hans de Graaff
2024-03-02 6:27 Hans de Graaff
2024-03-02 6:27 Hans de Graaff
2024-02-23 6:20 Hans de Graaff
2024-01-27 11:40 Hans de Graaff
2023-12-31 17:01 Arthur Zamarin
2023-12-31 17:01 Arthur Zamarin
2023-12-31 11:09 Hans de Graaff
2023-09-18 10:54 Sam James
2023-09-08 19:20 Hans de Graaff
2023-08-26 7:20 Hans de Graaff
2023-08-26 7:20 Hans de Graaff
2023-04-17 9:45 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-29 0:48 Sam James
2023-03-29 0:24 Sam James
2023-03-29 0:16 Sam James
2023-03-28 22:54 Sam James
2023-03-18 1:22 Sam James
2023-03-18 0:03 Sam James
2023-01-21 9:08 Hans de Graaff
2022-12-04 18:00 Arthur Zamarin
2022-12-03 17:37 Arthur Zamarin
2022-12-03 14:28 Arthur Zamarin
2022-12-03 14:28 Arthur Zamarin
2022-07-30 7:46 Hans de Graaff
2022-06-24 10:04 Hans de Graaff
2022-04-30 9:08 Hans de Graaff
2021-11-08 2:51 Yixun Lan
2021-10-31 4:45 Hans de Graaff
2021-04-10 6:17 Hans de Graaff
2020-08-23 11:45 David Seifert
2020-06-15 15:06 Agostino Sarubbo
2020-06-14 20:08 Sergei Trofimovich
2020-04-28 4:41 Hans de Graaff
2020-04-22 17:07 Sergei Trofimovich
2020-02-02 9:01 Hans de Graaff
2020-02-02 6:32 Hans de Graaff
2019-11-02 10:10 Hans de Graaff
2019-01-28 21:45 Hans de Graaff
2018-10-14 6:16 Hans de Graaff
2018-10-14 6:16 Hans de Graaff
2018-07-30 21:50 Sergei Trofimovich
2018-06-26 2:04 Aaron Bauman
2018-04-26 4:57 Hans de Graaff
2018-04-16 18:32 Hans de Graaff
2018-04-16 18:32 Hans de Graaff
2018-04-16 18:32 Hans de Graaff
2017-08-25 6:09 Hans de Graaff
2017-08-05 18:49 Hans de Graaff
2017-07-07 18:15 Alexis Ballier
2017-07-07 14:50 Agostino Sarubbo
2017-07-02 5:43 Hans de Graaff
2017-06-23 8:33 Agostino Sarubbo
2017-02-12 6:15 Hans de Graaff
2016-06-05 7:59 Hans de Graaff
2016-06-05 7:59 Hans de Graaff
2016-06-05 7:59 Hans de Graaff
2016-06-05 7:59 Hans de Graaff
2016-06-05 7:59 Hans de Graaff
2015-11-15 11:48 Manuel Rüger
2015-09-20 8:38 Jeroen Roovers
2015-09-08 1:12 Manuel Rüger
2015-09-07 9:57 Manuel Rüger
2015-09-06 13:25 Agostino Sarubbo
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=1468824488.5b2d958c16e9c079253c788869f419b04ce4d00b.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