On 06/07/2011 01:41 PM, Thiago Macieira wrote:
On Tuesday, 7 de June de 2011 10:14:43 Alexander Neundorf wrote:
On Tuesday, June 07, 2011 08:21:02 AM Sebastian Trüg wrote:
Just as a side-note on SDO: For me SDO is very close to the KDE
development process. If I had my way everyone running KDE
Just as a side-note on SDO: For me SDO is very close to the KDE
development process. If I had my way everyone running KDE master would
also use SDO master. But for some reason that would only be acceptable
if SDO were in KDE's git...
On 06/06/2011 06:53 PM, Thiago Macieira wrote:
On Monday, 6 de
On 06/06/2011 10:51 PM, Ben Cooksley wrote:
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
On Tuesday 07 June 2011 Jun, Sebastian Trüg wrote:
Restricting ourselves to old versions (and as a developer anything
released is old for me) means to restrict the power we have and
undermines our very development model.
In my opinion, almost always needing the development version of e.g. GTK
- Original Message -
IMHO it is out of the question to ask a developer to not implement a
great new feature just because the dependancies are too young.
I disagree completely. I would very much welcome a policy that states that you
can only depend on stuff that is available in the
On Tuesday, 7 de June de 2011 07:53:28 Tom Albers wrote:
- Original Message -
IMHO it is out of the question to ask a developer to not implement a
great new feature just because the dependancies are too young.
I disagree completely. I would very much welcome a policy that states
On Tuesday, June 07, 2011 09:32:09 AM Boudewijn Rempt wrote:
On Tuesday 07 June 2011 Jun, Sebastian Trüg wrote:
Restricting ourselves to old versions (and as a developer anything
released is old for me) means to restrict the power we have and
undermines our very development model.
In my
On Tuesday, 7 de June de 2011 10:14:43 Alexander Neundorf wrote:
On Tuesday, June 07, 2011 08:21:02 AM Sebastian Trüg wrote:
Just as a side-note on SDO: For me SDO is very close to the KDE
development process. If I had my way everyone running KDE master would
also use SDO master. But for
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
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
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
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 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
20 matches
Mail list logo
