From: "Diego Petteno (flameeyes)" <flameeyes@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-ruby/minitest: minitest-5.0.3.ebuild ChangeLog
Date: Fri, 31 May 2013 16:05:49 +0000 (UTC) [thread overview]
Message-ID: <20130531160549.573AD2171D@flycatcher.gentoo.org> (raw)
flameeyes 13/05/31 16:05:49
Modified: ChangeLog
Added: minitest-5.0.3.ebuild
Log:
Version bump, drop support for jruby for now.
(Portage version: 2.2.0_alpha176/cvs/Linux x86_64, signed Manifest commit with key 1CD13C8AD4301342)
Revision Changes Path
1.112 dev-ruby/minitest/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/minitest/ChangeLog?rev=1.112&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/minitest/ChangeLog?rev=1.112&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/minitest/ChangeLog?r1=1.111&r2=1.112
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-ruby/minitest/ChangeLog,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -r1.111 -r1.112
--- ChangeLog 7 May 2013 05:24:26 -0000 1.111
+++ ChangeLog 31 May 2013 16:05:49 -0000 1.112
@@ -1,6 +1,11 @@
# ChangeLog for dev-ruby/minitest
# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-ruby/minitest/ChangeLog,v 1.111 2013/05/07 05:24:26 graaff Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-ruby/minitest/ChangeLog,v 1.112 2013/05/31 16:05:49 flameeyes Exp $
+
+*minitest-5.0.3 (31 May 2013)
+
+ 31 May 2013; Diego E. Pettenò <flameeyes@gentoo.org> +minitest-5.0.3.ebuild:
+ Version bump, drop support for jruby for now.
*minitest-4.7.4 (07 May 2013)
1.1 dev-ruby/minitest/minitest-5.0.3.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/minitest/minitest-5.0.3.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/minitest/minitest-5.0.3.ebuild?rev=1.1&content-type=text/plain
Index: minitest-5.0.3.ebuild
===================================================================
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/dev-ruby/minitest/minitest-5.0.3.ebuild,v 1.1 2013/05/31 16:05:49 flameeyes Exp $
EAPI=5
USE_RUBY="ruby18 ruby19"
# Rake is the easiest way to go through this unfortunately.
RUBY_FAKEGEM_RECIPE_TEST="rake"
RUBY_FAKEGEM_TASK_DOC="docs"
RUBY_FAKEGEM_DOCDIR="doc"
RUBY_FAKEGEM_EXTRADOC="History.txt Manifest.txt README.txt"
inherit ruby-fakegem
DESCRIPTION="minitest/unit is a small and fast replacement for ruby's huge and slow test/unit."
HOMEPAGE="https://github.com/seattlerb/minitest"
LICENSE="MIT"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
IUSE="doc test"
ruby_add_bdepend "
doc? ( dev-ruby/hoe dev-ruby/rdoc )
ruby_targets_ruby18? ( !!dev-ruby/minitest[ruby_targets_ruby18] )"
# There is a nasty bug that tests fail if minitest is loaded already
# from the system.
reply other threads:[~2013-05-31 16:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130531160549.573AD2171D@flycatcher.gentoo.org \
--to=flameeyes@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