public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Manuel Rüger" <gentoo@rueg.eu>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/ruby-overlay:master commit in: dev-ruby/launchy/
Date: Wed, 29 May 2013 06:03:32 +0000 (UTC)	[thread overview]
Message-ID: <1369807195.dca0efab78f0767fd4424243d258e84dd104bb39.mrueg@gentoo> (raw)

commit:     dca0efab78f0767fd4424243d258e84dd104bb39
Author:     Manuel Rüger (mrueg) <gentoo <AT> rueg <DOT> eu>
AuthorDate: Wed May 29 05:59:55 2013 +0000
Commit:     Manuel Rüger <gentoo <AT> rueg <DOT> eu>
CommitDate: Wed May 29 05:59:55 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/ruby-overlay.git;a=commit;h=dca0efab

dev-ruby/launchy: Version bump

Package-Manager: portage-2.1.12.2

---
 dev-ruby/launchy/ChangeLog            |  8 ++++++--
 dev-ruby/launchy/launchy-2.3.0.ebuild | 29 +++++++++++++++++++++++++++++
 2 files changed, 35 insertions(+), 2 deletions(-)

diff --git a/dev-ruby/launchy/ChangeLog b/dev-ruby/launchy/ChangeLog
index 3c21c7a..a991b9b 100644
--- a/dev-ruby/launchy/ChangeLog
+++ b/dev-ruby/launchy/ChangeLog
@@ -1,7 +1,12 @@
 # ChangeLog for dev-ruby/launchy
-# Copyright 1999-2012 Gentoo Foundation; Distributed under the GPL v2
+# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+*launchy-2.3.0 (29 May 2013)
+
+  29 May 2013; Manuel Rueger (mrueg) gentoo@rueg.eu +launchy-2.3.0.ebuild:
+  dev-ruby/launchy: Version bump
+
 *launchy-2.1.2 (16 Dec 2012)
 
   16 Dec 2012; Hans de Graaff <graaff@gentoo.org> -launchy-0.3.5.ebuild,
@@ -17,4 +22,3 @@
 
   19 Jul 2011; Hans de Graaff <graaff@gentoo.org> +launchy-2.0.3.ebuild:
   Version bump. Not moving to main tree for same reason as flameeyes.
-

diff --git a/dev-ruby/launchy/launchy-2.3.0.ebuild b/dev-ruby/launchy/launchy-2.3.0.ebuild
new file mode 100644
index 0000000..1a142e9
--- /dev/null
+++ b/dev-ruby/launchy/launchy-2.3.0.ebuild
@@ -0,0 +1,29 @@
+# Copyright 1999-2013 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-ruby/will_paginate/will_paginate-2.3.11-r1.ebuild,v 1.2 2009/12/15 19:59:15 flameeyes Exp $
+
+EAPI=5
+USE_RUBY="ruby19"
+
+RUBY_FAKEGEM_EXTRADOC="README.md HISTORY.md"
+
+inherit ruby-fakegem
+
+DESCRIPTION="Helper class for launching cross-platform applications"
+HOMEPAGE="http://copiousfreetime.rubyforge.org/launchy/"
+
+LICENSE="ISC"
+
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE=""
+
+ruby_add_rdepend ">=dev-ruby/addressable-2.3"
+
+ruby_add_bdepend "test? ( >=dev-ruby/minitest-4.5.0
+	dev-ruby/simplecov )"
+
+# Tests fail, reported upstream. (Note for 2.0.3: can't find bug
+# report. Tests still fail). Wrong tests run on wrong OS. spoon
+# dependency unpackaged.
+RESTRICT=test


             reply	other threads:[~2013-05-29  6:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  6:03 Manuel Rüger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-23 15:17 [gentoo-commits] proj/ruby-overlay:master commit in: dev-ruby/launchy/ Manuel Rüger
2012-12-16  9:02 Hans de Graaff
2012-01-16 19:30 Hans de Graaff
2011-07-19  7:11 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=1369807195.dca0efab78f0767fd4424243d258e84dd104bb39.mrueg@gentoo \
    --to=gentoo@rueg.eu \
    --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