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: Thu, 29 Sep 2011 08:25:29 +0000 (UTC)	[thread overview]
Message-ID: <6084f56ca5863fd96904386e0fe290d9842d51b7.tetromino@gentoo> (raw)

commit:     6084f56ca5863fd96904386e0fe290d9842d51b7
Author:     Alexandre Rostovtsev <tetromino <AT> gmail <DOT> com>
AuthorDate: Thu Sep 29 07:46:15 2011 +0000
Commit:     Alexandre Restovtsev <tetromino <AT> gmail <DOT> com>
CommitDate: Thu Sep 29 07:46:15 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=6084f56c

dev-util/anjuta: 3.1.90 → 3.2.0

Version bump with numerous bug fixes and improvements. For now, on my
setup, tests appear to pass.

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

diff --git a/dev-util/anjuta/anjuta-3.1.90.ebuild b/dev-util/anjuta/anjuta-3.2.0.ebuild
similarity index 89%
rename from dev-util/anjuta/anjuta-3.1.90.ebuild
rename to dev-util/anjuta/anjuta-3.2.0.ebuild
index b91c70b..20e8c7f 100644
--- a/dev-util/anjuta/anjuta-3.1.90.ebuild
+++ b/dev-util/anjuta/anjuta-3.2.0.ebuild
@@ -17,15 +17,12 @@ SRC_URI="${SRC_URI} mirror://gentoo/introspection.m4.bz2"
 LICENSE="GPL-2"
 SLOT="0"
 KEYWORDS="~amd64 ~ppc ~sparc ~x86 ~x86-fbsd"
-IUSE="debug devhelp doc glade graphviz +introspection subversion test vala"
+IUSE="debug devhelp doc glade graphviz +introspection packagekit 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"
+# FIXME: tests are fragile and may require a specific set of USE flags
+#RESTRICT="test"
 
-RDEPEND=">=dev-libs/glib-2.28.0:2
+COMMON_DEPEND=">=dev-libs/glib-2.29.2:2
 	x11-libs/gdk-pixbuf:2
 	>=x11-libs/gtk+-3.0.0:3
 	>=x11-libs/vte-0.27.6:2.90
@@ -51,7 +48,9 @@ RDEPEND=">=dev-libs/glib-2.28.0:2
 		>=dev-libs/apr-1
 		>=dev-libs/apr-util-1 )
 	vala? ( >=dev-lang/vala-0.13.3:0.14 )"
-DEPEND="${RDEPEND}
+RDEPEND="${COMMON_DEPEND}
+	packagekit? ( app-admin/packagekit-base )"
+DEPEND="${COMMON_DEPEND}
 	>=dev-lang/perl-5
 	!!dev-libs/gnome-build
 	>=sys-devel/gettext-0.17
@@ -80,6 +79,7 @@ pkg_setup() {
 		$(use_enable glade plugin-glade)
 		$(use_enable graphviz)
 		$(use_enable introspection)
+		$(use_enable packagekit)
 		$(use_enable subversion plugin-subversion)
 		$(use_enable vala)"
 



             reply	other threads:[~2011-09-29  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29  8:25 Alexandre Restovtsev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-29  5:31 [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=6084f56ca5863fd96904386e0fe290d9842d51b7.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