From: "Manuel Rueger (mrueg)" <mrueg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-ruby/mixlib-shellout: mixlib-shellout-2.0.1.ebuild ChangeLog
Date: Fri, 17 Apr 2015 00:11:20 +0000 (UTC) [thread overview]
Message-ID: <20150417001121.A54221614A@oystercatcher.gentoo.org> (raw)
mrueg 15/04/17 00:11:20
Modified: ChangeLog
Added: mixlib-shellout-2.0.1.ebuild
Log:
Version bump.
(Portage version: 2.2.18/cvs/Linux x86_64, signed Manifest commit with key )
Revision Changes Path
1.14 dev-ruby/mixlib-shellout/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/mixlib-shellout/ChangeLog?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/mixlib-shellout/ChangeLog?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/mixlib-shellout/ChangeLog?r1=1.13&r2=1.14
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-ruby/mixlib-shellout/ChangeLog,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- ChangeLog 28 Feb 2015 15:48:07 -0000 1.13
+++ ChangeLog 17 Apr 2015 00:11:20 -0000 1.14
@@ -1,6 +1,11 @@
# ChangeLog for dev-ruby/mixlib-shellout
# Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-ruby/mixlib-shellout/ChangeLog,v 1.13 2015/02/28 15:48:07 mrueg Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-ruby/mixlib-shellout/ChangeLog,v 1.14 2015/04/17 00:11:20 mrueg Exp $
+
+*mixlib-shellout-2.0.1 (17 Apr 2015)
+
+ 17 Apr 2015; Manuel Rüger <mrueg@gentoo.org> +mixlib-shellout-2.0.1.ebuild:
+ Version bump.
28 Feb 2015; Manuel Rüger <mrueg@gentoo.org> -mixlib-shellout-1.3.0.ebuild,
-mixlib-shellout-1.4.0.ebuild, -mixlib-shellout-1.6.0.ebuild:
1.1 dev-ruby/mixlib-shellout/mixlib-shellout-2.0.1.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/mixlib-shellout/mixlib-shellout-2.0.1.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/mixlib-shellout/mixlib-shellout-2.0.1.ebuild?rev=1.1&content-type=text/plain
Index: mixlib-shellout-2.0.1.ebuild
===================================================================
# Copyright 1999-2015 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/dev-ruby/mixlib-shellout/mixlib-shellout-2.0.1.ebuild,v 1.1 2015/04/17 00:11:20 mrueg Exp $
EAPI=5
USE_RUBY="ruby19 ruby20 ruby21 ruby22"
RUBY_FAKEGEM_TASK_DOC=""
RUBY_FAKEGEM_RECIPE_TEST="rspec"
RUBY_FAKEGEM_EXTRA_DOC="README.md"
inherit ruby-fakegem
DESCRIPTION="Run external commands on Unix or Windows"
HOMEPAGE="http://github.com/opscode/mixlib-shellout"
SRC_URI="https://github.com/opscode/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="Apache-2.0"
SLOT="0"
KEYWORDS="~amd64 ~x86"
IUSE=""
each_ruby_prepare() {
# Make sure we actually use the right interpreter for testing
sed -i -e "/ruby_eval/ s:ruby :${RUBY} :" spec/mixlib/shellout_spec.rb || die
}
reply other threads:[~2015-04-17 0:11 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=20150417001121.A54221614A@oystercatcher.gentoo.org \
--to=mrueg@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