From: "Alexandre Restovtsev" <tetromino@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-shell/
Date: Wed, 27 Jul 2011 05:51:47 +0000 (UTC) [thread overview]
Message-ID: <40a28d2a2d9f4bac2e7aabf105e36407a36e0b8f.tetromino@gentoo> (raw)
commit: 40a28d2a2d9f4bac2e7aabf105e36407a36e0b8f
Author: Alexandre Rostovtsev <tetromino <AT> gmail <DOT> com>
AuthorDate: Wed Jul 27 04:30:47 2011 +0000
Commit: Alexandre Restovtsev <tetromino <AT> gmail <DOT> com>
CommitDate: Wed Jul 27 04:30:47 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=40a28d2a
gnome-base/gnome-shell: fix libXfixes dependency
libXfixes-5.0 needed for pointer barriers
---
gnome-base/gnome-shell/gnome-shell-3.0.2.ebuild | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/gnome-base/gnome-shell/gnome-shell-3.0.2.ebuild b/gnome-base/gnome-shell/gnome-shell-3.0.2.ebuild
index 14feacb..bd8fc7e 100644
--- a/gnome-base/gnome-shell/gnome-shell-3.0.2.ebuild
+++ b/gnome-base/gnome-shell/gnome-shell-3.0.2.ebuild
@@ -28,6 +28,7 @@ fi
# FIXME: Automagic gnome-bluetooth[introspection] support.
# latest gsettings-desktop-schemas is needed due to commit 602fa1c6
# latest g-c-c is needed due to https://bugs.gentoo.org/show_bug.cgi?id=360057
+# libXfixes-5.0 needed for pointer barriers
COMMON_DEPEND=">=dev-libs/glib-2.25.9:2
>=dev-libs/gjs-0.7.11
>=dev-libs/gobject-introspection-0.10.1
@@ -58,7 +59,7 @@ COMMON_DEPEND=">=dev-libs/glib-2.25.9:2
x11-libs/startup-notification
x11-libs/libX11
- x11-libs/libXfixes
+ >=x11-libs/libXfixes-5.0
x11-apps/mesa-progs"
# Runtime-only deps are probably incomplete and approximate.
# Each block:
next reply other threads:[~2011-07-27 6:02 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 5:51 Alexandre Restovtsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-26 22:14 [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-shell/ Mart Raudsepp
2018-09-26 22:14 Mart Raudsepp
2018-05-11 7:10 Sobhan Mohammadpour
2018-05-11 6:09 Sobhan Mohammadpour
2018-01-12 13:15 Dennis Lamm
2016-05-11 6:10 Remi Cardona
2016-03-25 0:56 Ole Reifschneider
2015-10-02 12:50 Ole Reifschneider
2015-09-13 22:52 Ole Reifschneider
2015-09-13 22:03 Ole Reifschneider
2015-05-14 18:22 Gilles Dartiguelongue
2015-04-23 7:05 Ole Reifschneider
2015-04-19 11:43 Ole Reifschneider
2014-12-26 21:53 Gilles Dartiguelongue
2014-11-24 7:26 Remi Cardona
2014-11-03 23:24 Gilles Dartiguelongue
2014-10-18 14:55 Gilles Dartiguelongue
2014-04-21 22:31 Gilles Dartiguelongue
2012-12-26 22:49 Gilles Dartiguelongue
2012-11-22 22:49 Gilles Dartiguelongue
2012-10-28 19:26 Alexandre Rostovtsev
2012-10-28 17:29 Gilles Dartiguelongue
2012-10-10 0:23 Alexandre Rostovtsev
2012-09-30 0:15 Alexandre Rostovtsev
2012-09-09 0:39 Nirbheek Chauhan
2012-09-03 18:32 Priit Laes
2012-07-21 18:01 Alexandre Restovtsev
2012-05-24 9:11 Alexandre Restovtsev
2012-04-20 7:12 Alexandre Restovtsev
2012-04-10 13:23 Priit Laes
2012-03-26 8:20 Nirbheek Chauhan
2011-10-21 2:14 Alexandre Restovtsev
2011-07-30 4:21 Alexandre Restovtsev
2011-06-07 20:58 Gilles Dartiguelongue
2011-05-30 17:11 Nirbheek Chauhan
2011-05-21 22:06 Nirbheek Chauhan
2011-05-21 18:37 Nirbheek Chauhan
2011-04-26 21:41 Gilles Dartiguelongue
2011-04-08 10:52 Gilles Dartiguelongue
2011-04-07 13:44 Nirbheek Chauhan
2011-04-05 21:38 Nirbheek Chauhan
2011-03-26 2:09 Nirbheek Chauhan
2011-03-23 6:11 Nirbheek Chauhan
2011-03-18 8:23 Nirbheek Chauhan
2011-03-15 18:02 Nirbheek Chauhan
2011-03-04 11:22 Nirbheek Chauhan
2011-02-25 23:34 Nirbheek Chauhan
2011-02-23 14:40 Nirbheek Chauhan
2011-02-21 11:44 Nirbheek Chauhan
2011-02-21 7:17 Nirbheek Chauhan
2011-02-18 6:31 Nirbheek Chauhan
2011-02-18 4:40 Nirbheek Chauhan
2011-02-12 10:24 Nirbheek Chauhan
2011-02-12 9:30 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=40a28d2a2d9f4bac2e7aabf105e36407a36e0b8f.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