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:master commit in: media-libs/cogl/
Date: Sat,  1 Oct 2011 04:39:54 +0000 (UTC)	[thread overview]
Message-ID: <8008e14ea6fa430ba6ddf9ed17fc5f3531a8d1e2.tetromino@gentoo> (raw)

commit:     8008e14ea6fa430ba6ddf9ed17fc5f3531a8d1e2
Author:     Alexandre Rostovtsev <tetromino <AT> gmail <DOT> com>
AuthorDate: Sat Oct  1 04:38:09 2011 +0000
Commit:     Alexandre Restovtsev <tetromino <AT> gmail <DOT> com>
CommitDate: Sat Oct  1 04:38:09 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=8008e14e

media-libs/cogl: replace old clutter blocker with !<

As pointed out by Olivier Crete on IRC, a '!<' blocker will allow
portage to automatically update clutter despite file collisions.

---
 media-libs/cogl/cogl-1.8.0.ebuild |    2 +-
 media-libs/cogl/cogl-9999.ebuild  |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/media-libs/cogl/cogl-1.8.0.ebuild b/media-libs/cogl/cogl-1.8.0.ebuild
index adf4366..83eccfd 100644
--- a/media-libs/cogl/cogl-1.8.0.ebuild
+++ b/media-libs/cogl/cogl-1.8.0.ebuild
@@ -39,7 +39,7 @@ COMMON_DEPEND=">=dev-libs/glib-2.26.0:2
 	pango? ( >=x11-libs/pango-1.20.0[introspection?] )"
 # before clutter-1.7, cogl was part of clutter
 RDEPEND="${COMMON_DEPEND}
-	!!<media-libs/clutter-1.7"
+	!<media-libs/clutter-1.7"
 DEPEND="${COMMON_DEPEND}
 	dev-util/pkgconfig
 	sys-devel/gettext

diff --git a/media-libs/cogl/cogl-9999.ebuild b/media-libs/cogl/cogl-9999.ebuild
index adf4366..83eccfd 100644
--- a/media-libs/cogl/cogl-9999.ebuild
+++ b/media-libs/cogl/cogl-9999.ebuild
@@ -39,7 +39,7 @@ COMMON_DEPEND=">=dev-libs/glib-2.26.0:2
 	pango? ( >=x11-libs/pango-1.20.0[introspection?] )"
 # before clutter-1.7, cogl was part of clutter
 RDEPEND="${COMMON_DEPEND}
-	!!<media-libs/clutter-1.7"
+	!<media-libs/clutter-1.7"
 DEPEND="${COMMON_DEPEND}
 	dev-util/pkgconfig
 	sys-devel/gettext



             reply	other threads:[~2011-10-01  4:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-01  4:39 Alexandre Restovtsev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-18  7:37 [gentoo-commits] proj/gnome:master commit in: media-libs/cogl/ Alexandre Restovtsev
2011-10-29 19:41 Alexandre Restovtsev
2012-09-15  7:53 Alexandre Rostovtsev
2012-09-16  7:44 Alexandre Rostovtsev
2012-10-27 19:40 Gilles Dartiguelongue
2012-12-19  0:39 Alexandre Rostovtsev
2013-01-19 21:38 Alexandre Rostovtsev
2013-03-15  7:38 Priit Laes
2013-12-19 23:40 Gilles Dartiguelongue
2014-04-15 22:05 Gilles Dartiguelongue
2014-10-12 23:19 Gilles Dartiguelongue
2014-11-03 23:24 Gilles Dartiguelongue
2014-12-07 23:08 Gilles Dartiguelongue
2014-12-08 21:57 Gilles Dartiguelongue
2014-12-26 21:47 Gilles Dartiguelongue
2015-04-18  9:00 Ole Reifschneider
2015-06-09  9:16 Gilles Dartiguelongue
2015-09-13 22:03 Ole Reifschneider
2016-01-30 17:33 Priit Laes
2018-01-12 14:00 Dennis Lamm

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=8008e14ea6fa430ba6ddf9ed17fc5f3531a8d1e2.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