public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] dev/graaff:master commit in: dev-ruby/ri_cal/
Date: Fri, 28 Nov 2014 15:13:15 +0000 (UTC)	[thread overview]
Message-ID: <1417187576.69bba1ab307bcf69abca7e9d43fdc3f7126242c9.graaff@gentoo> (raw)

commit:     69bba1ab307bcf69abca7e9d43fdc3f7126242c9
Author:     Hans de Graaff <hans <AT> degraaff <DOT> org>
AuthorDate: Fri Nov 28 15:12:56 2014 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Fri Nov 28 15:12:56 2014 +0000
URL:        http://sources.gentoo.org/gitweb/?p=dev/graaff.git;a=commit;h=69bba1ab

EAPI=5. ruby20.

Package-Manager: portage-2.2.8-r2

---
 dev-ruby/ri_cal/ChangeLog              |  5 ++++
 dev-ruby/ri_cal/ri_cal-0.8.8-r2.ebuild | 45 ++++++++++++++++++++++++++++++++++
 2 files changed, 50 insertions(+)

diff --git a/dev-ruby/ri_cal/ChangeLog b/dev-ruby/ri_cal/ChangeLog
index c5aabd0..87a4177 100644
--- a/dev-ruby/ri_cal/ChangeLog
+++ b/dev-ruby/ri_cal/ChangeLog
@@ -2,6 +2,11 @@
 # Copyright 1999-2014 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+*ri_cal-0.8.8-r2 (28 Nov 2014)
+
+  28 Nov 2014; Hans de Graaff <graaff@gentoo.org> +ri_cal-0.8.8-r2.ebuild:
+  EAPI=5. ruby20.
+
   01 Jul 2014; Hans de Graaff <graaff@gentoo.org> ri_cal-0.8.8-r1.ebuild:
   Remove ruby18, ree18.
 

diff --git a/dev-ruby/ri_cal/ri_cal-0.8.8-r2.ebuild b/dev-ruby/ri_cal/ri_cal-0.8.8-r2.ebuild
new file mode 100644
index 0000000..6e0e2ae
--- /dev/null
+++ b/dev-ruby/ri_cal/ri_cal-0.8.8-r2.ebuild
@@ -0,0 +1,45 @@
+# Copyright 1999-2014 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header:  $
+
+EAPI=5
+USE_RUBY="ruby19 ruby20"
+
+RUBY_FAKEGEM_TASK_TEST=""
+
+# requires jeweler/ad_agency
+RUBY_FAKEGEM_TASK_DOC=""
+RUBY_FAKEGEM_DOCDIR="doc"
+RUBY_FAKEGEM_EXTRADOC="docs/* History.txt README.txt"
+
+inherit ruby-fakegem
+
+DESCRIPTION="A new Ruby implementation of RFC2445 iCalendar."
+HOMEPAGE="http://github.com/rubyredrick/ri_cal"
+LICENSE="MIT"
+
+KEYWORDS="~amd64"
+SLOT="0"
+IUSE=""
+
+RUBY_PATCHES=( ${P}-rails32.patch )
+
+# This gem can use either tzinfo or activesupport and thus doesn't have
+# any explicit dependency. We always depend on tzinfo since newer
+# versions of activesupport do this as well.
+ruby_add_rdepend "dev-ruby/tzinfo"
+
+ruby_add_bdepend "test? ( dev-ruby/rspec:0 )"
+
+each_ruby_test() {
+	case ${RUBY} in
+		*ruby20)
+			# A few specs fail on UTF-8 stuff. Doesn't look problematic.
+			# Not fixing this properly since I intend to move back to
+			# icalendar anyway.
+			;;
+		*)
+			${RUBY} -S spec spec || die
+			;;
+	esac
+}


             reply	other threads:[~2014-11-28 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 15:13 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-14 20:09 [gentoo-commits] dev/graaff:master commit in: dev-ruby/ri_cal/ Hans de Graaff
2016-02-14 20:09 Hans de Graaff
2016-02-14 20:09 Hans de Graaff
2014-07-02  7:56 Hans de Graaff
2013-08-30  9:23 Hans de Graaff
2013-08-30  9:23 Hans de Graaff
2012-04-30  9:30 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=1417187576.69bba1ab307bcf69abca7e9d43fdc3f7126242c9.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