public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Manuel Nickschas" <sputnick@quassel-irc.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: kde-base/kwin/
Date: Tue, 23 Aug 2011 09:34:40 +0000 (UTC)	[thread overview]
Message-ID: <6ae34bfbfa552ac025dfaaaedbefa972d8a4f8df.sput@gentoo> (raw)

commit:     6ae34bfbfa552ac025dfaaaedbefa972d8a4f8df
Author:     Manuel Nickschas <sputnick <AT> quassel-irc <DOT> org>
AuthorDate: Tue Aug 23 09:33:20 2011 +0000
Commit:     Manuel Nickschas <sputnick <AT> quassel-irc <DOT> org>
CommitDate: Tue Aug 23 09:33:55 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=commit;h=6ae34bfb

[kwin:live] GLES currently requires OpenGL to build

---
 kde-base/kwin/kwin-9999.ebuild |    7 +++++--
 1 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/kde-base/kwin/kwin-9999.ebuild b/kde-base/kwin/kwin-9999.ebuild
index 1b47860..6cf683f 100644
--- a/kde-base/kwin/kwin-9999.ebuild
+++ b/kde-base/kwin/kwin-9999.ebuild
@@ -47,8 +47,11 @@ PATCHES=(
 	"${FILESDIR}/${PN}-4.4.2-xinerama_cmake_automagic.patch"
 )
 
-# you can use just gles or opengl or none
-REQUIRED_USE="opengl? ( !gles ) gles? ( !opengl )"
+# normally, you can use just gles or opengl or none
+#REQUIRED_USE="opengl? ( !gles ) gles? ( !opengl )"
+
+# right now, upstream requires opengl to always be enabled with gles
+REQUIRED_USE="gles? ( opengl )"
 
 src_configure() {
 	# FIXME Remove when activity API moved away from libkworkspace



             reply	other threads:[~2011-08-23  9:34 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23  9:34 Manuel Nickschas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-02 19:08 [gentoo-commits] proj/kde:master commit in: kde-base/kwin/ Manuel Rüger
2014-12-02 13:57 Michael Palimaka
2014-10-10 15:44 Michael Palimaka
2014-09-19 20:20 Johannes Huber
2014-08-09 15:22 Michael Palimaka
2014-08-09 15:22 Michael Palimaka
2014-07-26 17:52 Marc Schiffbauer
2014-07-21 20:14 Michael Palimaka
2014-07-15 16:52 Michael Palimaka
2014-06-24 14:44 Michael Palimaka
2014-06-16 14:21 Michael Palimaka
2014-05-08 13:10 Johannes Huber
2014-04-15  7:43 Johannes Huber
2014-04-06 13:48 Johannes Huber
2014-04-05 13:51 Michael Palimaka
2014-04-04 18:08 Michael Palimaka
2014-04-04 17:51 Michael Palimaka
2014-04-04 17:28 Michael Palimaka
2014-04-04 16:54 Michael Palimaka
2014-04-04 16:36 Michael Palimaka
2013-09-25 18:55 Johannes Huber
2013-08-29 15:52 Michael Palimaka
2013-08-19 14:04 Michael Palimaka
2013-07-23 19:53 Johannes Huber
2013-07-23 14:04 Michael Palimaka
2013-07-20 15:05 Johannes Huber
2013-07-20 13:42 Johannes Huber
2013-07-12  8:12 Patrick Lauer
2013-06-20 20:24 Andreas Hüttel
2013-06-20 20:14 Andreas Hüttel
2013-06-07 21:35 Johannes Huber
2013-05-19 15:44 Michael Palimaka
2013-04-09 19:22 Michael Palimaka
2012-09-05 11:19 Michael Palimaka
2012-07-27 17:21 Andreas Hüttel
2012-06-11  8:29 Johannes Huber
2012-03-07 17:16 Andreas Hüttel
2011-12-23 16:20 Andreas Hüttel
2011-09-25 19:35 Andreas Hüttel
2011-09-22 15:25 Manuel Nickschas
2011-05-25 20:18 Jorge Manuel B. S. Vicetto
2011-05-16 22:54 Jonathan Callen
2011-05-16 22:54 Jonathan Callen
2011-05-01 19:49 Tomas Chvatal

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=6ae34bfbfa552ac025dfaaaedbefa972d8a4f8df.sput@gentoo \
    --to=sputnick@quassel-irc.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