public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alexandre Restovtsev" <tetromino@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:gnome-next commit in: dev-util/anjuta/
Date: Mon, 29 Aug 2011 05:31:15 +0000 (UTC)	[thread overview]
Message-ID: <652d893aed07ca68527c4c9b27473ca4a29570fb.tetromino@gentoo> (raw)

commit:     652d893aed07ca68527c4c9b27473ca4a29570fb
Author:     Alexandre Rostovtsev <tetromino <AT> gmail <DOT> com>
AuthorDate: Mon Aug 29 05:19:19 2011 +0000
Commit:     Alexandre Restovtsev <tetromino <AT> gmail <DOT> com>
CommitDate: Mon Aug 29 05:26:29 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=652d893a

dev-util/anjuta: 3.1.5 → 3.1.90

Version bump with numerous changes. Now uses libgda:5 and vala-0.13.3.

Forced to restrict tests because there is no way to pass them on Gentoo:
1. tests require plugins/am-project/tests/anjuta.lst to run, but this
file is not distributed with tarballs (see https://bugzilla.gnome.org/show_bug.cgi?id=657589);
2. in any case, anjuta.lst in upstream git is currently out of date (needs
to be updated for vala:0.14 and libgda:5, for example);
3. and, as far as I can tell, the tests will only pass when anjuta is
built with a specific set of USE flags.

Need to think of a way of handling this...

---
 .../{anjuta-3.1.5.ebuild => anjuta-3.1.90.ebuild}  |   10 ++++++++--
 1 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/dev-util/anjuta/anjuta-3.1.5.ebuild b/dev-util/anjuta/anjuta-3.1.90.ebuild
similarity index 90%
rename from dev-util/anjuta/anjuta-3.1.5.ebuild
rename to dev-util/anjuta/anjuta-3.1.90.ebuild
index 6ccd352..b91c70b 100644
--- a/dev-util/anjuta/anjuta-3.1.5.ebuild
+++ b/dev-util/anjuta/anjuta-3.1.90.ebuild
@@ -19,6 +19,12 @@ SLOT="0"
 KEYWORDS="~amd64 ~ppc ~sparc ~x86 ~x86-fbsd"
 IUSE="debug devhelp doc glade graphviz +introspection subversion test vala"
 
+# FIXME: tests do not work. First, anjuta.lst is missing from tarballs (see
+# upstream bug 657589). Second, in any case, anjuta.lst is out of date (no
+# vala:0.14, no libgda:5). Third, AFAICT, the tests could only pass if anjuta
+# is built a specific set of USE flags.
+RESTRICT="test"
+
 RDEPEND=">=dev-libs/glib-2.28.0:2
 	x11-libs/gdk-pixbuf:2
 	>=x11-libs/gtk+-3.0.0:3
@@ -29,7 +35,7 @@ RDEPEND=">=dev-libs/glib-2.28.0:2
 
 	sys-devel/autogen
 
-	>=gnome-extra/libgda-4.2.0:4
+	>=gnome-extra/libgda-4.99.0:5
 	dev-util/ctags
 
 	x11-libs/libXext
@@ -44,7 +50,7 @@ RDEPEND=">=dev-libs/glib-2.28.0:2
 		>=net-libs/neon-0.28.2
 		>=dev-libs/apr-1
 		>=dev-libs/apr-util-1 )
-	vala? ( >=dev-lang/vala-0.13.0:0.14 )"
+	vala? ( >=dev-lang/vala-0.13.3:0.14 )"
 DEPEND="${RDEPEND}
 	>=dev-lang/perl-5
 	!!dev-libs/gnome-build



             reply	other threads:[~2011-08-29  5:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29  5:31 Alexandre Restovtsev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-09-29  8:25 [gentoo-commits] proj/gnome:gnome-next commit in: dev-util/anjuta/ Alexandre Restovtsev
2011-08-13  6:37 Alexandre Restovtsev
2011-07-26 18:47 Alexandre Restovtsev
2011-07-24 20:19 Alexandre Restovtsev
2011-07-24 20:19 Alexandre Restovtsev

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=652d893aed07ca68527c4c9b27473ca4a29570fb.tetromino@gentoo \
    --to=tetromino@gmail.com \
    --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