---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101509/#review3714
---
This review has been submitted with commit
Hi all,
I am requesting that a moratorium on dependency bumps for dependencies
which are hard to build be enacted. This would affect system wide
components which rely on root access and are heavily integrated into
the system. This would not affect things such as UPower or the like -
which aren't
On Monday 06 June 2011 23:05:52 Ben Cooksley wrote:
Hi all,
I am requesting that a moratorium on dependency bumps for dependencies
which are hard to build be enacted. This would affect system wide
components which rely on root access and are heavily integrated into
the system. This would
On Monday, 6 de June de 2011 17:48:41 Martin Gräßlin wrote:
Personal opinion: I think it is impossible to want to run the latest
software around an old stack. The overall FOSS world is rolling release
with everything depending on everything. I cannot see why you want to
change that with a
On Tuesday, June 7, 2011 06:19:52 Ben Cooksley wrote:
The Moratorium would extend to all components of the KDE SC
distribution. Hence kde-core-devel.
imho this is impossible, for the reasons Martin noted.
The components affected by the Moratorium - namely the Kernel, X and
ALSA interfaces
On Tue, Jun 7, 2011 at 8:06 AM, Aaron J. Seigo ase...@kde.org wrote:
On Tuesday, June 7, 2011 06:19:52 Ben Cooksley wrote:
The Moratorium would extend to all components of the KDE SC
distribution. Hence kde-core-devel.
imho this is impossible, for the reasons Martin noted.
The components
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101527/#review3726
---
i doubt this fix is correct. what looks more like is
On Monday, June 06, 2011 08:05:41 PM Luca Beltrame wrote:
In data Monday 06 June 2011 19:26:38, Sebastian Kügler ha scritto:
(I took the liberty of adding kde-bindings to the CC of tihs specific
topic)
We want to make it possible to use our frameworks in Qt projects without
On Tue, Jun 7, 2011 at 8:42 AM, Martin Gräßlin mgraess...@kde.org wrote:
On Tuesday 07 June 2011 08:29:51 Ben Cooksley wrote:
Next KWin. It currently depends upon Mesa 7.10. I have a local revert
in a private local branch which reverts the dependency check code
within KWin to continue to allow
On Monday, June 06, 2011 05:48:41 PM Martin Gräßlin wrote:
...
Personal opinion: I think it is impossible to want to run the latest
software around an old stack. The overall FOSS world is rolling release
with everything depending on everything.
You cannot say it like that.
It depends always on
On Monday, June 06, 2011 09:41:43 PM Richard Dale wrote:
I started another QtScript bindings project called 'JSmoke' which is
currently stalled because of technical problems with QtScript which got
even worse moving from Qt 4.5 to 4.6. That did cover both the Qt and KDE
apis, and I really
Please also note that I will add a runtime requirement to Mesa 7.11 as I
have here on my system
the start of the Wayland port which will be in 4.8 and requires Mesa 7.11.
Why would wayland support have any effect on runtime dependency on X11?
Am Mon, 6 Jun 2011 17:08:24 -0400
schrieb Maksim Orlovich m...@cornell.edu:
Why would wayland support have any effect on runtime dependency on
X11?
http://groups.google.com/group/wayland-display-server/web/building-and-running-wayland
Building mesa
Wayland uses the mesa EGL stack, and all
Hello lists,
disclaimer
As, Sebas pointed out we've been meeting here to work on plans to improve our
frameworks offering leading to the decision of leaving the current kdelibs
model behind and prepare for a more modular suite named KDE Frameworks. If
you didn't read his email yet, please do
Am Tue, 7 Jun 2011 08:51:26 +1200
schrieb Ben Cooksley bcooks...@kde.org:
You are effectively classifying a distribution
No, distribution version vanilla - iff at all.
(You still can develop on master, even run kwin - just not use OpenGL
composited kwin from master then - that's not quite the
Am Mon, 6 Jun 2011 18:33:28 -0400
schrieb Maksim Orlovich m...@cornell.edu:
Sorry, my wording was poor:
Might have been my reading as well. Your original question could have
perfectly been read like the clarified one.
OK, wayland needs recent Mesa at runtime,
but I am not running Wayland; so
On 6 June 2011 23:36, Scott Kitterman k...@kitterman.com wrote:
I get we need to modularize for a number of important reasons, but I don't
see
the companion story for how this all gets released as something coherent
and
functional.
Where's that part of the story?
Scott K
From Sebas'
Hello lists,
disclaimer
As, Sebas pointed out we've been meeting here to work on plans to improve our
frameworks offering leading to the decision of leaving the current kdelibs
model behind and prepare for a more modular suite named KDE Frameworks. If
you didn't read his email yet, please do
On Tuesday 7 June 2011 00:17:23 Albert Astals Cid wrote:
A Monday, June 06, 2011, Kevin Ottens va escriure:
Hello lists,
Throughout this example we will refer to the following graph:
http://files.kde.org/ervin/platform11/kde-frameworks-dependencies-plan.pd
f
Shall i read from this
On Tuesday 7 June 2011 01:26:17 Albert Astals Cid wrote:
A Tuesday, June 07, 2011, Kevin Ottens va escriure:
Well, obviously a Tier 1 framework would have to use tr() instead of
i18n() for its translation needs.
Are we still going to use .po or you plan on us moving to Qt translation
* all new features will be developed using the recommended git workflow
(pending publication; Cornelius is working on that one);
Those rules might seem like a strong departure from what we're used to. On
the other hand, if you look at them closely, they are merely making explicit
changes to
On Monday, June 6, 2011 19:41:15 Maksim Orlovich wrote:
* all new features will be developed using the recommended git
workflow
(pending publication; Cornelius is working on that one);
Those rules might seem like a strong departure from what we're used to.
On the other hand, if
Scott Kitterman wrote:
New thread as requested.
I've been told on IRC that we will still have an integrated release of
what used to be KDE (I've no clue what to call it now since I think I read
KDE SC was deprecated).
All I see in the messaging from the platform sprint seems to be about
On June 6, 2011, 8:38 p.m., Aaron J. Seigo wrote:
i doubt this fix is correct. what looks more like is
KStatusNotifierItemDBus::~KStatusNotifierItemDBus(). right now this is the
implementation:
m_dbus.unregisterService(m_service);
and perhaps it should include:
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101520/
---
Review request for KDE Runtime and Michael Jansen.
Summary
---
On June 6, 2011, 2:04 a.m., David Faure wrote:
Looks good overall, but I think I found a bug with negative coordinates:
konqueror --geometry +500-100
gives me a window that xwininfo says is at 744x533+500-29, which doesn't
match.
I have no experience with this, but it seems to me
On June 6, 2011, 8:38 p.m., Aaron J. Seigo wrote:
i doubt this fix is correct. what looks more like is
KStatusNotifierItemDBus::~KStatusNotifierItemDBus(). right now this is the
implementation:
m_dbus.unregisterService(m_service);
and perhaps it should include:
On Tue, Jun 7, 2011 at 5:12 PM, Martin Gräßlin mgraess...@kde.org wrote:
- Ursprüngliche Mitteilung -
On 6/6/11, Thomas Lübking thomas.luebk...@gmail.com wrote:
Am Mon, 6 Jun 2011 17:08:24 -0400
schrieb Maksim Orlovich m...@cornell.edu:
Why would wayland support have any effect
On Fri, Jun 3, 2011 at 10:12 PM, Stefan Majewsky
stefan.majew...@googlemail.com wrote:
Hi,
I've been looking into QML again for kdegames. Some background: I
added a QDeclarativeImageProvider to feed images from libtagaro's
ThemeProvider into QML, and that mostly works (with an emphasis on
Hi all,
You've probably been aware that a rather sizable group of KDE developers and
stakeholders in our development platform is meeting in Randa, Switzerland to
discuss the future of our development frameworks, with the big topic being
modularization of kdelibs. We've had a number of great
Error building kde/kanagram from master, the output:
[ 22%] Building CXX object
kanagram/src/CMakeFiles/kanagram.dir/kanagram.o
/home/mmodem/rpm/BUILD/kdeedu/kanagram/src/kanagram.cpp:49:30: fatal
error: sharedkvtmlfiles.h: No such file or directory
compilation terminated.
make[2]: ***
Le Monday 6 June 2011 19:35:53, Zé a écrit :
Error building kde/kanagram from master, the output:
[ 22%] Building CXX object
kanagram/src/CMakeFiles/kanagram.dir/kanagram.o
/home/mmodem/rpm/BUILD/kdeedu/kanagram/src/kanagram.cpp:49:30: fatal
error: sharedkvtmlfiles.h: No such file or
On Monday, June 06, 2011 08:05:41 PM Luca Beltrame wrote:
In data Monday 06 June 2011 19:26:38, Sebastian Kügler ha scritto:
(I took the liberty of adding kde-bindings to the CC of tihs specific
topic)
We want to make it possible to use our frameworks in Qt projects without
On Monday, June 06, 2011 09:41:43 PM Richard Dale wrote:
I started another QtScript bindings project called 'JSmoke' which is
currently stalled because of technical problems with QtScript which got
even worse moving from Qt 4.5 to 4.6. That did cover both the Qt and KDE
apis, and I really
On Tue, 7 Jun 2011 08:36:52 AM Scott Kitterman wrote:
The results on the platform sprint read like more chaos is coming.
I get we need to modularize for a number of important reasons, but I don't
see the companion story for how this all gets released as something
coherent and functional.
In data Monday 06 June 2011 19:26:38, Sebastian Kügler ha scritto:
(I took the liberty of adding kde-bindings to the CC of tihs specific topic)
We want to make it possible to use our frameworks in Qt projects without
significant additional dependencies. This means:
Reading around the plans
Hello lists,
disclaimer
As, Sebas pointed out we've been meeting here to work on plans to improve our
frameworks offering leading to the decision of leaving the current kdelibs
model behind and prepare for a more modular suite named KDE Frameworks. If
you didn't read his email yet, please do
Hello lists,
disclaimer
As, Sebas pointed out we've been meeting here to work on plans to improve our
frameworks offering leading to the decision of leaving the current kdelibs
model behind and prepare for a more modular suite named KDE Frameworks. If
you didn't read his email yet, please do
John Layt johnl...@googlemail.com wrote:
On 6 June 2011 23:36, Scott Kitterman k...@kitterman.com wrote:
I get we need to modularize for a number of important reasons, but I
don't
see
the companion story for how this all gets released as something
coherent
and
functional.
Where's that
On Tuesday, June 7, 2011 00:51:12 todd rme wrote:
As for new threads, are you looking for suggestions and ideas or only
questions at this point?
we're looking for feedback on the topics that are presented in these emails
(there are a few others that have already been sent, and some that will
Nicolas Alvarez nicolas.alva...@gmail.com wrote:
Scott Kitterman wrote:
New thread as requested.
I've been told on IRC that we will still have an integrated release
of
what used to be KDE (I've no clue what to call it now since I think I
read
KDE SC was deprecated).
All I see in the
Okay, I feel like this should be a very simple thing to accomplish.
However, I can't seem to figure out how to do it. In my CMakeLists.txt
file I have the following lines to install images:
install(FILES images/close.svgz DESTINATION
42 matches
Mail list logo
