My idea about this concerns the way we let other people know aboout new
features. I usually read our feature plan (e.g.
http://techbase.kde.org/Schedules/KDE4/4.11_Feature_Plan).
I think we could add one general page per project, similar to that one,
listing:
- the feature
- the branch where it is
On Thursday 04 July 2013 01:28:16 Aaron J. Seigo wrote:
On Tuesday, June 25, 2013 10:10:03 Aurélien Gâteau wrote:
Why would the code be specific to kiosk? - You asked for an example, not
justification.
I asked for an example, you provided one about kiosk, I answer how your
kiosk
Le lundi 8 juillet 2013 11:47:03 Thomas Lübking a écrit :
Escalating to the High Council.
:-)
KWin needs[1] to set some environment variables before libGL is
instantiated.
Instantiated = loaded as a directly-linked shared library?
Or is it dlopened? (then a Q_CONSTRUCTOR_FUNCTION would
On Monday 08 July 2013 23:08:29 Ingo Klöcker wrote:
On Monday 08 July 2013 22:14:28 Aurélien Gâteau wrote:
On Monday 08 July 2013 16:26:00 laurent Montel wrote:
Le lundi 8 juillet 2013 16:11:05 Frank Reininghaus a écrit :
Hi,
2013/7/8 Àlex Fiestas:
Now that kde-workspace
On Friday 05 July 2013 Jul 15:34:06 Sven Brauch wrote:
2. GDK installs a deadly X error handler, causing the application to
exit, instead of just printing an error message. See multiple
backtraces containing gdk_x_error[3]
There have recently been similar reports for KDevelop, too.
On Monday 08 July 2013 20:35:22 Luca Beltrame wrote:
(apologies for breaking your threading, but I'm not subscribed to k-c-d; in
fact, please CC me with replies, thanks!)
Currently, the people working on openSUSE packages are against the proposal.
A detailed explanation follows.
First and
On Monday 08 July 2013 22:01:29 Andrea Scarpino wrote:
We don't just run a sed rule on each spec (pkgbuild, in my case) file. We
check for new dependencies (resp. dependencies not needed anymore), new
modules (resp. modules not part of the SC anymore), build failure, etc...
Can't we do
On Monday 08 July 2013 20:16:16 Scott Kitterman wrote:
For Kubuntu (also mostly volunteer effort), it took about two weeks to
package the 4.11 beta. For generating package updates for already existing
packages, we have a script that will produce initial packages.
This is quite fast, should be
On Monday 08 July 2013 20:40:59 Heinz Wiesinger wrote:
Any reason not to CC kde-packager or kde-release-team? IMHO they'd be
primary audiences for this.
kde-packagers is a private mailist, I'm not sure how to handle it.
kde-release-team, I assumed they were in kde-core-devel as well, but you
On Dienstag, 9. Juli 2013 10:51:16 CEST, David Faure wrote:
Instantiated = loaded as a directly-linked shared library?
Yes.
Interesting hack, never heard of that before.
Afaics Lubos added it.
If you set LD_PRELOAD and then type kwin in a terminal, it
still doesn't work?
No.
Then the
On Tuesday, July 09, 2013 12:05:30 PM Àlex Fiestas wrote:
On Monday 08 July 2013 22:01:29 Andrea Scarpino wrote:
We don't just run a sed rule on each spec (pkgbuild, in my case) file. We
check for new dependencies (resp. dependencies not needed anymore), new
modules (resp. modules not part
On Tuesday, July 09, 2013 12:11:48 PM Àlex Fiestas wrote:
On Monday 08 July 2013 20:16:16 Scott Kitterman wrote:
For Kubuntu (also mostly volunteer effort), it took about two weeks to
package the 4.11 beta. For generating package updates for already
existing
packages, we have a script
On Tuesday 09 July 2013 06:33:21 Scott Kitterman wrote:
On Tuesday, July 09, 2013 12:05:30 PM Àlex Fiestas wrote:
On Monday 08 July 2013 22:01:29 Andrea Scarpino wrote:
We don't just run a sed rule on each spec (pkgbuild, in my case) file.
We
check for new dependencies (resp.
On Tuesday 09 July 2013 06:33:21 Scott Kitterman wrote:
On Tuesday, July 09, 2013 12:05:30 PM Àlex Fiestas wrote:
On Monday 08 July 2013 22:01:29 Andrea Scarpino wrote:
We don't just run a sed rule on each spec (pkgbuild, in my case) file.
We
check for new dependencies (resp.
On Tuesday 09 July 2013 06:43:48 Scott Kitterman wrote:
I want the point releases. The reasons for wanting them are for
consistency, marketing, and for distro policy releases its' much easier to
get a set of packages that are part of a release through the post distro
release QA process than a
From my point of view, 3 month releases are going to actually increase
quality. At least in Nepomuk.
The Nepomuk developers (me included) have often merged feature
branches right before the feature freeze even if the branch has some
problems. No one wants to wait 8 months (2 months for the
On Tue, Jul 9, 2013 at 12:38 PM, Martin Gräßlin mgraess...@kde.org wrote:
On Tuesday 09 July 2013 06:33:21 Scott Kitterman wrote:
On Tuesday, July 09, 2013 12:05:30 PM Àlex Fiestas wrote:
On Monday 08 July 2013 22:01:29 Andrea Scarpino wrote:
We don't just run a sed rule on each spec
On Tue, Jul 9, 2013 at 4:13 PM, Scott Kitterman k...@kitterman.com wrote:
These all have to be test compiled, checked for new or missing files,
checked for files that have moved between packages, checked for
license/copyright updates, etc.
I guess you have all this mostly automagically
On Tue, Jul 9, 2013 at 9:14 AM, Vishesh Handa wrote:
On Tue, Jul 9, 2013 at 4:13 PM, Scott Kitterman wrote:
These all have to be test compiled, checked for new or missing files,
checked for files that have moved between packages, checked for
license/copyright updates, etc.
I guess you
Vishesh Handa m...@vhanda.in wrote:
On Tue, Jul 9, 2013 at 4:13 PM, Scott Kitterman k...@kitterman.com
wrote:
These all have to be test compiled, checked for new or missing
files,
checked for files that have moved between packages, checked for
license/copyright updates, etc.
I guess you
On Tue, Jul 9, 2013 at 5:58 PM, Scott Kitterman k...@kitterman.com wrote:
There I'd a licensecheck script that does this. It helps, but the results
have to be checked and properly documented and so thete is still substantial
manual work required. KDE packages are generally better about
On Tue, Jul 9, 2013 at 2:28 PM, Scott Kitterman k...@kitterman.com wrote:
Could you please elaborate why the licensing stuff cannot be
automatically done?
There I'd a licensecheck script that does this. It helps, but the results
have to be checked and properly documented and so thete is still
On Tue, Jul 9, 2013 at 2:34 PM, Vishesh Handa m...@vhanda.in wrote:
On Tue, Jul 9, 2013 at 5:58 PM, Scott Kitterman k...@kitterman.com wrote:
There I'd a licensecheck script that does this. It helps, but the results
have to be checked and properly documented and so thete is still substantial
On Tue, Jul 9, 2013 at 6:08 PM, Harald Sitter sit...@kde.org wrote:
there would not be any problem. But reality diverges :(
I'm all for fixing this in at least KDE SC. That way if/when we have
shorter releases you can have some kind of guarantee that you will not
encounter strange behaviours
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111462/
---
Review request for kdelibs and David Faure.
Description
---
The
On 2013-07-09, Vishesh Handa m...@vhanda.in wrote:
On Tue, Jul 9, 2013 at 6:08 PM, Harald Sitter sit...@kde.org wrote:
there would not be any problem. But reality diverges :(
I'm all for fixing this in at least KDE SC. That way if/when we have
shorter releases you can have some kind of
Hi,
[...] (just replying at some point)
Two point I want to mention:
1) working in a branch for kdepim is quite painful, as you need actually work
on branches of 3 (or sometimes 4) modules: kdepimlibs, kdepim-runtime, kdepim
(and akonadi). Keep them up-to-date, merge them at the right point,
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111462/#review35788
---
To save 2 stat() per second, you want the user to not be
On Tuesday 09 July 2013 13:50:59 Harald Sitter wrote:
On Tue, Jul 9, 2013 at 12:38 PM, Martin Gräßlin mgraess...@kde.org wrote:
On Tuesday 09 July 2013 06:33:21 Scott Kitterman wrote:
On Tuesday, July 09, 2013 12:05:30 PM Àlex Fiestas wrote:
On Monday 08 July 2013 22:01:29 Andrea Scarpino
On Tuesday 09 July 2013 13:07:33 Sune Vuorela wrote:
On 2013-07-09, Vishesh Handa m...@vhanda.in wrote:
On Tue, Jul 9, 2013 at 6:08 PM, Harald Sitter sit...@kde.org wrote:
there would not be any problem. But reality diverges :(
I'm all for fixing this in at least KDE SC. That way if/when
On Tuesday 09 July 2013 14:54:38 Harald Sitter wrote:
yes, not releated to schedules directly. the problem however is more
social than anything. people mostly don't care enough. like not adding
a fully copy of the GPL.
if you buy some router running Linux you will get with it a printed
copy
On 2013-07-09, Àlex Fiestas afies...@kde.org wrote:
If we keep copyright holders and licence, we can change the structure of the
header, no?
We can.
/Sune
On Tuesday 09 July 2013 16:12:35 Andras Mantia wrote:
I also find the motivation somewhat contradictory. Yes, you want to provide
new features faster, but by cutting down testing time. *Are you sure?*
Well here we have to ask whether the current testing procedure works. Since
the beta got
Hello everyone,
This is the minutes of the Week 28 KF5 meeting. As usual it has been held on
#kde-devel at 4pm Paris time.
Were present: afiestas, apol, ben2367, dfaure, sebas, svuorela, wojtask9 and
myself.
Announcements:
* Akademy next week so no meeting on #kde-devel
* Instead we'll have
On Tuesday 09 July 2013 16:12:35 Andras Mantia wrote:
Hi,
[...] (just replying at some point)
Two point I want to mention:
1) working in a branch for kdepim is quite painful, as you need actually
work on branches of 3 (or sometimes 4) modules: kdepimlibs, kdepim-runtime,
kdepim (and
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110043/#review35800
---
Important: the bug is not fixed forever. In Qt5,
So the kde-workspace dudes decided they don't want a 4.12 release and that
they'll do a LTS 4.11, fine, how do we fix that branch wise?
Cheers,
Albert
On Dienstag, 9. Juli 2013 10:51:16 CEST, David Faure wrote:
Then the problem is elsewhere.
Yes, seems. Sorry for the noise.
Compiling kwin as regular exec brought no change.
The nvidiahack lib is inoperative for other reasons.
We'll have to find another solution for the issue.
Cheers,
Thomas
On Tuesday 09 July 2013 09:36:00 andrea diamantini wrote:
My idea about this concerns the way we let other people know aboout
new features. I usually read our feature plan (e.g.
http://techbase.kde.org/Schedules/KDE4/4.11_Feature_Plan).
I think we could add one general page per project,
On Tuesday 09 July 2013, Sven Brauch wrote:
I think Nuno's point is very interesting and worth thinking about. To
stick with the firefox example, since they started releasing every
ortography fix in the settings dialog as a new major version, I think
attention in the media to their releases
On Tuesday 09 July 2013, Andras Mantia wrote:
Hi,
[...] (just replying at some point)
Two point I want to mention:
1) working in a branch for kdepim is quite painful, as you need actually
work on branches of 3 (or sometimes 4) modules: kdepimlibs,
kdepim-runtime, kdepim (and akonadi).
On Tuesday 09 July 2013, Àlex Fiestas wrote:
On Tuesday 09 July 2013 13:50:59 Harald Sitter wrote:
On Tue, Jul 9, 2013 at 12:38 PM, Martin Gräßlin mgraess...@kde.org
wrote:
On Tuesday 09 July 2013 06:33:21 Scott Kitterman wrote:
On Tuesday, July 09, 2013 12:05:30 PM Àlex Fiestas wrote:
On Tuesday 09 July 2013, Àlex Fiestas wrote:
...
What we need then is:
-Be Have a strict policy on using always using find_package
if somewhere a package which is used without being searched for this is and
always was a build system bug.
Alex
On Tuesday 09 July 2013, Àlex Fiestas wrote:
On Monday 08 July 2013 20:35:22 Luca Beltrame wrote:
(apologies for breaking your threading, but I'm not subscribed to k-c-d;
in fact, please CC me with replies, thanks!)
Currently, the people working on openSUSE packages are against the
On Tuesday 09 July 2013 18:57:41 Albert Astals Cid wrote:
So the kde-workspace dudes decided they don't want a 4.12 release and that
they'll do a LTS 4.11, fine, how do we fix that branch wise?
I don't see how that affects branching.
* 4.11 is branched from master
* master is opened for feature
On Tuesday, July 09, 2013 12:52:04 PM Àlex Fiestas wrote:
On Tuesday 09 July 2013 06:43:48 Scott Kitterman wrote:
I want the point releases. The reasons for wanting them are for
consistency, marketing, and for distro policy releases its' much easier to
get a set of packages that are part
On Tue, Jul 9, 2013 at 11:30 AM, Boudewijn Rempt b...@valdyas.org wrote:
On Friday 05 July 2013 Jul 15:34:06 Sven Brauch wrote:
2. GDK installs a deadly X error handler, causing the application to
exit, instead of just printing an error message. See multiple
backtraces containing
On Monday 08 July 2013 18:59:12 Michael Pyne wrote:
On Mon, July 8, 2013 17:45:10 Philip Muskovac wrote:
What would at least make my life easier here would be a way to easily get a
list of all patches that were applied to a stable release (esp. when someone
bothers to backport a fix after
On Tuesday 09 July 2013 12:03:30 Àlex Fiestas wrote:
On Monday 08 July 2013 20:35:22 Luca Beltrame wrote:
(apologies for breaking your threading, but I'm not subscribed to k-c-d; in
fact, please CC me with replies, thanks!)
Currently, the people working on openSUSE packages are against
On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
* master is opened for feature development and will lead to Plasma
Workspaces 2 (or whatever the release will be called in the end).
Does this mean that kde-workspace in master will exists, but with a different
content (and I
On July 5, 2013, 2:23 p.m., David Faure wrote:
kio/kio/scheduler.cpp, line 766
http://git.reviewboard.kde.org/r/111335/diff/2/?file=167766#file167766line766
Please don't put this code in scheduler.cpp
I'm trying to properly split core and gui aspects of KIO in
51 matches
Mail list logo
