On Thursday, July 11, 2013 06:53:51 PM andrea diamantini wrote:
What about a single official development branch?
Just use two branches:
- master branch (stable)
- kdevel branch (devel)
The natural question to come is: why isn't master the devel branch? :)
Ok, let me reformulate again: did we
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,
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 Tuesday, November 06, 2012 09:08:36 AM Jaime Torres Amate wrote:
On Nov. 6, 2012, 6:46 a.m., David Edmundson wrote:
The responsibility of deleting d-rootDir seems to lie within KArchive.
Therefore by setting the rootDir twice either implicitly or explicitly
(which this assert is
Kevin Krammer wrote:
Hi Guy,
On Friday, 2012-11-02, guy-kde wrote:
Hello again!
Using
https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/
entry/experimental/libkdeclarative/kdeclarative.h
I think kdelibs/master is currently unused (not updated). Try branch
On Wednesday, October 24, 2012 11:48:08 PM Alex Fiestas wrote:
On Wednesday 24 October 2012 23:19:57 Andras Mantia wrote:
Hi,
Aaron J. Seigo wrote:
Bodega
I hope you are aware about the meaning of the name in certain countries.
:)
In Spain it is winery, while in Romania
On Tuesday, October 09, 2012 07:56:48 PM Laszlo Papp wrote:
On Tue, Oct 9, 2012 at 7:54 PM, Laszlo Papp lp...@kde.org wrote:
I think David took the responsibility for the merge:
http://lists.kde.org/?l=kde-release-teamm=134510779413123w=4
Oh, that was mentioned for kdelibs, and not
On Thursday, October 04, 2012 12:49:34 PM Stephen Kelly wrote:
The distros people are using to develop KDE 4.10 ship with CMake 2.8.7 (eg
latest Ubuntu). I think that's a more significant fact.
it is hard to understand for me why this is a so hard argument. Building KDE
already requires
Hi,
Akonadi is a server application without KDE dependencies and originally was
designed to not show any user-visible strings, except in debug logs.
Unfortunately the way it evolved resulted in some error messages going into
user visible message boxes. These strings are currently not
On Thursday, September 06, 2012 02:34:32 PM you wrote:
On Thursday 30 August 2012 20:35:02 Andras Mantia wrote:
On Thursday, August 30, 2012 11:51:07 AM Allen Winter wrote:
We discussed this on IRC last night.
The only downside we could come up with was extra disk space needed
On Wednesday, August 22, 2012 01:58:57 PM David Edmundson wrote:
- a big refactor (see branch big_refactor)
Without going into other details: what would be the reason to merge LightDM
*now*, if you have a big refactoring undergoing?
Andras
On Wednesday, July 25, 2012 06:10:21 AM Laszlo Papp wrote:
(sorry for sounding blunt but
Windows should not really be considered as something unimportnat for
KDE in my opinion).
There was never a requirement for software that wants to be part of KDE to
work on Windows, and I'd like to keep
On Wednesday, July 25, 2012 08:57:13 AM Laszlo Papp wrote:
There was never a requirement for software that wants to be part of KDE to
work on Windows, and I'd like to keep this as it is.
Perhaps, but I can still raise my personal opinion, just as you can
Sure. :)
.
Although, it is a bit
On Sunday, July 01, 2012 09:21:08 AM Albert Astals Cid wrote:
I disagree, as a matter of fact, I don't have internet connection in the
room in my hostel, so if i had a need to use krita I'd need to read its
manual (since my painting/drawing skills are null) and i'd be not happy to
discover I
James Booth wrote:
For future reference for anyone else that has this problem, Andras's
suggestion worked. Thanks!
Sorry, I forgot to send to the list (didn't check the To field).
Did you make a bug report?
Andras
On Sunday, July 01, 2012 12:15:05 PM Andras Mantia wrote:
James Booth wrote:
For future reference for anyone else that has this problem, Andras's
suggestion worked. Thanks!
Sorry, I forgot to send to the list (didn't check the To field).
And now it is wrong list. I suck. :(
Andras
On Thursday, April 12, 2012 10:49:10 PM Alexander Neundorf wrote:
Yes, how good squish works for you depends on at least two things:
We also use Squish, and it found bugs and regressions in our code.
Still, there is a big problem with it: the test needs to be maintained
constantly. If they are
On Saturday, February 25, 2012 09:47:56 PM Thomas Lübking wrote:
Am 25.02.2012, 21:38 Uhr, schrieb Andras Mantia aman...@kde.org:
What about
QT_PLUGIN_PATH=/opt/kde4/lib64/kde4/plugins: strace kwrite --style
oxygen
21 | grep -i oxygen | grep open
On Saturday, February 25, 2012 11:42:13 AM Hugo Pereira Da Costa wrote:
I tend to think proper soversion bumping would be a good solution.
In both cases it does not fix (sorry for repeating myself) the true
issue, which is that your plugin_path is not consistent with your
LD_LIBRARY_PATH.
On Saturday, February 25, 2012 08:37:05 PM Thomas Lübking wrote:
Tell me what do I do wrongly, and I'm willing to apologize and fix my
system.
try
QT_PLUGIN_PATH=/opt/kde4/lib64/kde4/plugins:/usr/lib64/kde4/plugins strace
kwrite --style oxygen 21 | grep -i oxygen | grep open
On Saturday, February 25, 2012 09:11:08 PM Thomas Lübking wrote:
Yupp, wild guess:
move the Trolltech.conf away, it usually contains a lot of caching junk
(from old Qt versions, installations ...) and try again (somewhere the
wrong path has to derive from)
I did remove that countless
On Saturday, February 25, 2012 09:25:36 PM Thomas Lübking wrote:
Am 25.02.2012, 21:15 Uhr, schrieb Andras Mantia aman...@kde.org:
I did remove that countless times while trying to find a solution...
Meaning it is /not/ there when the simple env path launch fails?
Yes.
What about
On Thursday, February 23, 2012 04:57:16 PM David Edmundson wrote:
First of all, the bugzilla is supposed to be a communication tool between
the user and the developer.
Or is it?
If I understand Martin correctly, he wants bugzilla to be a list of
things broken in my app, not a
On Tuesday, February 21, 2012 11:37:23 PM Milian Wolff wrote:
What version will the new bugzilla have? Are the REST/JSON/XMLRPC APIs
going to be enabled?
And then maybe someone can revive kbugbuster.
Andras
On Friday, February 24, 2012 11:51:51 AM Thiago Macieira wrote:
Correct.
Make sure that your new KDE's installation is found by the Qt plugin
system, either by setting QT_PLUGIN_PATH or by editing Trolltech.conf.
I have this:
printenv QT_PLUGIN_PATH
On Friday, February 24, 2012 12:01:37 PM Hugo Pereira Da Costa wrote:
are other applications also crashing (like, e.g. plasma workspace, or
kwin) ? (It should)
if not it might be a QtCreator specific issue.
Yes, also kde apps crash, like kdesvn, kate, etc.
Andras
On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote:
Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia aman...@kde.org:
Bugzilla is not a to-do list, it is for what else... a bug (and wishlist)
reporting tool for users.
The problem here that this is noise prone and the low entropy
On Friday, February 24, 2012 06:51:11 PM Martin Gräßlin wrote:
- first level support
issues are not opened on the bug tracker but in a user support management
system - e.g. forums.kde.org. Only if the supporters figure out that there
is a real bug, they will open a bug report. This is high
On Friday, February 24, 2012 07:28:33 PM Martin Gräßlin wrote:
User asking on distro/KDE mailinglist/forum/IRC because xyz does not work.
1. he gets an answer
1.1 known bug
1.2 me too - the user might open a bug report
1.3 it works like this…
2. he does not get an answer
On Friday, February 24, 2012 05:48:36 PM Sune Vuorela wrote:
On 2012-02-24, Hugo Pereira Da Costa h...@oxygen-icons.org wrote:
I understand that. The point I was trying to make, is that you would
still get the old pluggin, admittingly without crashing, but which
would nonetheless be not
On Wednesday, February 22, 2012 04:11:57 PM David Faure wrote:
He asked me why we don't do this, and the only reply I could come
up with was the few cases where bugs turned into actual political
flamewars; his answer was obviously give rights to everyone, and remove
rights when someone
On Tuesday, November 29, 2011 17:29:33 Thomas =?ISO-8859-1?Q?L=FCbking?=
wrote:
Ok, last observation:
The critical value seems to be 13 in Bespin (what means
PM_ScrollBarExtent to be 15 for horizontal sliders)
The value of qcommonstyle is qMax(16, QApplication::globalStrut());
FYI, this
On Thursday, November 17, 2011 18:17:30 Alexander Neundorf wrote:
i was not sure i agreed with that approach, but i have to say that
the last few threads on this topic on k-c-d have supported their
point :(
I would draw exactly the opposite conclusion.
If the signal to noise ratio here
On Wednesday, November 16, 2011 09:48:15 Thomas Friedrichsmeier wrote:
So why have this discussion on a separate list, at all? Isn't that
just the� sort of topic that kde-core-devel is for?
I agree...
Andras
Testing
---
Thanks,
Andras Mantia
On Tuesday, October 11, 2011 16:33:39 Thomas L�bking wrote:
Also it's not required to have the terminal on top of the stack - i've
always been very successful abusing MMB cp to clickpaste me any
command i wanted ;-)
Seems I'm not alone doing that. :)
Andras
On Saturday, October 01, 2011 23:13:06 Dario Freddi wrote:
Is it? Certainly disabling desktop effects and 3D acceleration has
an
impact.
Sorry to disappoint you, but this action will be removed in 4.8.
Martin has explicitely stated that for how compositing in KDE works
now turning off
On Sunday, October 02, 2011 17:04:50 Martin Gr��lin wrote:
So please calmn down and lets focus on improving the user experience
by not spending too much time on too long� threads.
I'm far from being upset or anything. I just gave my opinion, which
seems to match others as well. We were *asked*
On Saturday, October 01, 2011 16:27:48 Dario Freddi wrote:
Hello all, and sorry for cross-posting.
[...]
I can't comment on activities, never used them, nor feel the need to use
them. So this sounds more like the power management applet would force
me to create and use activites.
What I can
On Saturday, October 01, 2011 14:43:24 Michael Pyne wrote:
I can say that on my laptop I've used the power management widget all
the� time, but the only times I've touched Activities has been
completely by accident, since I use the laptop for basically one
thing. So while Activities should
[Please reply on both lists if you cross-posted, otherwise dicussion will be
more fragmented. I just looked up the plasma list out of curiosity, normally
I don't follow, so your mail would have been missed.]
Dario Freddi wrote:
I can't comment on activities, never used them, nor feel the need
On Thursday, September 29, 2011 21:43:34 Stefan Majewsky wrote:
Without judging on the other arguments which look very reasonable to
me...
On Thu, Sep 29, 2011 at 2:01 PM, Kevin Kofler kevin.kof...@chello.at
wrote:
2. It will be confusing to our users, and even to some packagers, to
have a
(I reply to the list only, as it is not related to the request itself)
And no, we definitely want no nested event loop. Anything else, but
not that.
I agree 100%. When you see things like the same modal messagebox popping
up twice (so one is visible, and another one appears called from the
On Wednesday, February 02, 2011 18:36:28 Alexander Neundorf wrote:
I don't really care how it will be, but I really think we should agree
on one common recommended and documented workflow to use.
I agree of having a recommended way of doing, but I do not agree forcing
a predefined workflow on
Hi,
I compiled KDE trunk and installed in a clean install dir. For some
reason kdebase compilation failed and I saw that kdesdk also failed.
Looking at the log it shows that kdesdk depends on kdebase, because
dolphin-plugins/git and svn looks for libkonq. I think this should not
happen
On 2010-12-01 17:23:11, Kevin Ottens wrote:
Well, if the job is explicitely isAutoDelete() then I'd say it's a bug in
the caller to try to delete it in the first place...
Aurélien Gâteau wrote:
I see your point, but on the other hand if the job is not *autodelete*
and the slot
46 matches
Mail list logo
