From: "Nirbheek Chauhan" <nirbheek@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: dev-libs/gjs/
Date: Thu, 31 Mar 2011 13:52:01 +0000 (UTC) [thread overview]
Message-ID: <2a1fca74d3c4fe60e6f457e92c60dbc452554089.nirbheek@gentoo> (raw)
commit: 2a1fca74d3c4fe60e6f457e92c60dbc452554089
Author: Nirbheek Chauhan <nirbheek <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 30 13:16:41 2011 +0000
Commit: Nirbheek Chauhan <nirbheek <AT> gentoo <DOT> org>
CommitDate: Wed Mar 30 13:16:41 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=2a1fca74
dev-libs/gjs: always block against spidermonkey, bug 361287
---
dev-libs/gjs/gjs-0.7.13.ebuild | 2 +-
dev-libs/gjs/gjs-9999.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-libs/gjs/gjs-0.7.13.ebuild b/dev-libs/gjs/gjs-0.7.13.ebuild
index 530dfb5..53dca9f 100644
--- a/dev-libs/gjs/gjs-0.7.13.ebuild
+++ b/dev-libs/gjs/gjs-0.7.13.ebuild
@@ -35,7 +35,7 @@ DEPEND="${RDEPEND}
coverage? (
sys-devel/gcc
dev-util/lcov )
- test? ( !dev-lang/spidermonkey )"
+ !dev-lang/spidermonkey"
# HACK HACK: gjs-tests picks up /usr/lib/libmozjs.so with spidermonkey installed
src_prepare() {
diff --git a/dev-libs/gjs/gjs-9999.ebuild b/dev-libs/gjs/gjs-9999.ebuild
index 530dfb5..53dca9f 100644
--- a/dev-libs/gjs/gjs-9999.ebuild
+++ b/dev-libs/gjs/gjs-9999.ebuild
@@ -35,7 +35,7 @@ DEPEND="${RDEPEND}
coverage? (
sys-devel/gcc
dev-util/lcov )
- test? ( !dev-lang/spidermonkey )"
+ !dev-lang/spidermonkey"
# HACK HACK: gjs-tests picks up /usr/lib/libmozjs.so with spidermonkey installed
src_prepare() {
next reply other threads:[~2011-03-31 13:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 13:52 Nirbheek Chauhan [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-23 20:37 [gentoo-commits] proj/gnome:master commit in: dev-libs/gjs/ Mart Raudsepp
2019-02-23 20:37 Mart Raudsepp
2018-09-10 21:33 Gilles Dartiguelongue
2018-03-02 17:35 Sobhan Mohammadpour
2017-12-20 23:00 Sobhan Mohammadpour
2015-06-09 13:48 Gilles Dartiguelongue
2014-12-21 13:28 Gilles Dartiguelongue
2014-10-05 22:09 Gilles Dartiguelongue
2014-04-21 22:31 Gilles Dartiguelongue
2014-04-15 22:05 Gilles Dartiguelongue
2013-12-22 23:38 Gilles Dartiguelongue
2013-11-24 22:07 Gilles Dartiguelongue
2012-09-25 15:46 Alexandre Rostovtsev
2012-09-05 15:48 Nirbheek Chauhan
2012-08-18 12:41 Priit Laes
2012-08-18 12:09 Priit Laes
2012-04-02 3:30 Alexandre Restovtsev
2012-03-31 9:14 Nirbheek Chauhan
2012-03-21 18:27 Alexandre Restovtsev
2012-03-07 0:32 Alexandre Restovtsev
2012-03-07 0:08 Alexandre Restovtsev
2012-02-27 4:47 Alexandre Restovtsev
2011-07-30 16:38 Alexandre Restovtsev
2011-04-09 16:26 Priit Laes
2011-04-09 7:04 Nirbheek Chauhan
2011-04-08 10:52 Gilles Dartiguelongue
2011-04-05 0:57 Nirbheek Chauhan
2011-04-05 0:57 Nirbheek Chauhan
2011-03-12 3:19 Nirbheek Chauhan
2011-02-27 3:02 Jonathan Callen
2011-02-23 14:40 Nirbheek Chauhan
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=2a1fca74d3c4fe60e6f457e92c60dbc452554089.nirbheek@gentoo \
--to=nirbheek@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