From: "Hans de Graaff (graaff)" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-ruby/execjs: execjs-2.2.0.ebuild ChangeLog
Date: Sat, 7 Jun 2014 05:39:44 +0000 (UTC) [thread overview]
Message-ID: <20140607053944.CDEEE2004E@flycatcher.gentoo.org> (raw)
graaff 14/06/07 05:39:44
Modified: ChangeLog
Added: execjs-2.2.0.ebuild
Log:
Version bump.
(Portage version: 2.2.8-r1/cvs/Linux x86_64, signed Manifest commit with key 0x8883FA56A308A8D7!)
Revision Changes Path
1.18 dev-ruby/execjs/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/execjs/ChangeLog?rev=1.18&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/execjs/ChangeLog?rev=1.18&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/execjs/ChangeLog?r1=1.17&r2=1.18
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-ruby/execjs/ChangeLog,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- ChangeLog 28 May 2014 05:50:08 -0000 1.17
+++ ChangeLog 7 Jun 2014 05:39:44 -0000 1.18
@@ -1,6 +1,11 @@
# ChangeLog for dev-ruby/execjs
# Copyright 1999-2014 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-ruby/execjs/ChangeLog,v 1.17 2014/05/28 05:50:08 graaff Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-ruby/execjs/ChangeLog,v 1.18 2014/06/07 05:39:44 graaff Exp $
+
+*execjs-2.2.0 (07 Jun 2014)
+
+ 07 Jun 2014; Hans de Graaff <graaff@gentoo.org> +execjs-2.2.0.ebuild:
+ Version bump.
*execjs-2.1.0 (28 May 2014)
1.1 dev-ruby/execjs/execjs-2.2.0.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/execjs/execjs-2.2.0.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-ruby/execjs/execjs-2.2.0.ebuild?rev=1.1&content-type=text/plain
Index: execjs-2.2.0.ebuild
===================================================================
# Copyright 1999-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/dev-ruby/execjs/execjs-2.2.0.ebuild,v 1.1 2014/06/07 05:39:44 graaff Exp $
EAPI=5
USE_RUBY="ruby19 ruby20 ruby21"
RUBY_FAKEGEM_TASK_DOC=""
RUBY_FAKEGEM_EXTRADOC="README.md"
RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
inherit ruby-fakegem
DESCRIPTION="ExecJS lets you run JavaScript code from Ruby"
HOMEPAGE="https://github.com/sstephenson/execjs"
SRC_URI="https://github.com/sstephenson/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="MIT"
SLOT="0"
KEYWORDS="~amd64 ~arm ~x86 ~x64-macos"
IUSE="test"
# execjs supports various javascript runtimes. They are listed in order
# as per the documentation. For now only include the ones already in the
# tree.
# therubyracer, therubyrhino, node.js, spidermonkey (deprecated)
# spidermonkey doesn't pass the test suite:
# https://github.com/sstephenson/execjs/issues/62
RDEPEND+=" || ( net-libs/nodejs )"
all_ruby_prepare() {
# Avoid test requiring network connectivity. We could potentially
# substitute dev-ruby/coffee-script-source for this.
sed -i -e '/test_coffeescript/,/end/ s:^:#:' test/test_execjs.rb || die
}
reply other threads:[~2014-06-07 5:39 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=20140607053944.CDEEE2004E@flycatcher.gentoo.org \
--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