On 2025-06-02, Ben Cooksley wrote:
> As launching VMs is not the most efficient approach for all workloads,
> limited support for running Docker containers will be preserved, however
> this support is primarily intended for running linters, sanity checks and
> website builds, and is not intended f
On 2025-06-03, Ben Cooksley wrote:
> Not sure why we're wanting to monitor for compilation on an Ubuntu LTS
> specifically, would have thought that was something best watched by our
> Appimage CD builds. Those are currently performed on a SLES image.
The purpose is to test that one can do applica
On 2024-11-04, Sune Vuorela wrote:
[looks like half a sentence disappeared between brain and keyboard]
> On a more 'matter of taste'-note, it does look like someone has went
> overboard with templates. While I like and understand templates,
I think this might be a bit too much an
On 2024-11-03, Neal Gompa wrote:
> It's not that simple. The reason I suggested MPL-2.0 is because
> LGPL-2.1-or-later is effectively the same as GPL-2.0-or-later with
> Rust because it's statically linked.
>
> MPL-2.0 preserves the copyleft at a per source file level, but allows
> the binary arti
On 2024-11-01, Carl Schwan wrote:
> This is a KDE Review request for md4qt. md4qt is a Markdown parser
> for Qt projects.
Where do you expect it to 'land' ? Frameworks? apps/libraries?
What api compatibilities are expected?
What does it do that Qt's markdown support in QTD doesn't do?
Which ma
On 2024-11-03, Harald Sitter wrote:
> Currently we have two sets of duplicated metadata one in the ksb format and
> one in yaml. Nico wants to only have one, and I for one agree with this.
I really think the ksb or yaml format files aren't metadata files, but
configuration files and doesn't belon
On 2024-11-03, christ...@cullmann.io wrote:
> kde-builder in no drop in replacement, at least for me.
>
> I and others discussed that close to infinitely in the past with the
> kde-builder maintainer.
I agree here.
What KDE-Builder at least needs is
- all code changes being actually reviewed.
On 2024-10-30, Darshan Phaldesai wrote:
> Few considerations:
> First, I plan to include bridges for most libraries needed for
> application development and so need to consider their licenses as well.
> Second, This project will only hold the "bridge" code and thus users
> will still need to ins
On Mon, Apr 8, 2024 at 10:05 AM wrote:
> and deprecating the kdesrc-build. That way we can move forward with new tool.
I don't think reviewing or not of kde-builder should have any effect on
kdesrc-build.
I think also we should be slightly wary of changing a long-running 20y
old tool written by
On 2024-02-13, Harald Sitter wrote:
> Do you have a testing plan in mind?
Not a dedicated one, no. But assuming your analysis is mostly correct,
something along the lines of
- What's the plasma startup performance with and without sycoca on a
clean user
- If much slower, try isolate whic
On 2024-02-08, Harald Sitter wrote:
> It occurs to me that we should ponder sycoca a bit.
>
> Currently the sycoca contains 3 types of caches:
At some point I remember David Faure, iirc as part of his QMimeType
work, removed part of sycoca, but left the remaining bits as a per
user cache *becaus
On 2024-01-29, Jonathan Riddell wrote:
> This sort of comment makes me really sad. The All About the Apps goal,
> which in principle is still ongoing, was an attempt to get KDE developers
> to realise it was important not just to write apps but to actually make
> them available to users, I find i
On 2024-01-17, Danilo Agostini wrote:
> It allows the user, through the use of a keyboard shortcut or a dolphin
> servicemenu, to have a quick preview of the files that are shown in the
> folder without having to open the default application.
>
> Similar applications are Gnome Sushi and Quick Look
On 2023-10-01, Carl Schwan wrote:
> Hello,
>
> I started writting a small application to generate and compare files with
> their
> checksum two years. I piked it up again recently and I think this is now
> ready
> for a kde review.
Even two years ago, checking stuff with md5 was not a good id
On 2021-12-19, Nate Graham wrote:
> For what it's worth, I don't think server-wise retracing is solely a
> workaround for distro-specific issues. Even for distros that ship debug
> symbols, I often find in my bug triaging that it can be a challenge to
> get users to actually use them.
Server s
On 2020-04-12, Dimitris Kardarakos wrote:
>
> Hello everyone,
>
> I'd like to let you know that the Calindori [1] application has been
> moved to kdereview.
I'm a bit curious about the name. Is it just a random butchering of
Calendar or does it actually have a meaning?
/Sune
On 2019-05-09, Jonathan Riddell wrote:
> I'd like to propose moving krecipes to unmaintained. It still uses
> kdelibs4 and has had no feature commits since 2016.
I'd like to gentle promote KookBook here ... it has a krecipes converter
should anyone feel stuck with their data.
/Sune
On 2018-06-04, Alexander Volkov wrote:
> This can be made optional, as it is done in Qt.
> So distros will have a choice whether to install qmlc files or not.
> Debian installs them.
I think Debian only installs the qmlc files for Qt packages (where the
versioning already is tightly coupled to Qt
On 2018-02-07, Matthieu Gallien wrote:
> I have updated the readme. I still do not know if it is possible to properly
> check for them at build time
It doesn't make sense to do build time checks for runtime dependencies,
other than as an informal notice.
The build is for distributions happening
On 2017-03-28, Boudewijn Rempt wrote:
> I'm now wondering whether to hack QSaveFile's close to just not
> abort, or add inherits("QSaveFile") checks all over KArchive --
> or whether there's a third, better option that I've missed...
Without having put too much thought into it, add an "Don't clos
o the patch.
konqueror/src/CMakeLists.txt
<https://git.reviewboard.kde.org/r/128941/#comment66844>
I think the comment is wrong. I can't find any zlib references in konqueror
itself. Also note that the linkage is actually commented out.
- Sune Vuorela
On Sept. 18, 2016, 11:
On 2015-09-27, Boudhayan Gupta wrote:
> "Seen before" is no reason to not move forward if we can actually fix
> this. As I said, Extragear library developers will *have* to provide
> API/ABI guarantees.
Good luck with that.
> That's the ideal scenario, but isn't becoming a framework... hard?
No
On 2015-09-27, Boudhayan Gupta wrote:
> What I propose is that all libraries which want to manage their own
> release cycles and their own namespaces, be moved to Extragear Libs
> and release from there. All the libraries which can stick to the
> Applications release-unit, move to Support or a new
On 2015-09-26, Boudhayan Gupta wrote:
> We could kill two birds with one stone here, creating a new KDE module
> just for libraries (say, KDE Companion Libraries or something) and put
> everything in the KC5 (or whatever we decide) namespace.
By doing this, we kind of make it a thing to .. become
On 2015-09-26, Alexander Potashev wrote:
> 1. Many people prefer a "KF5" prefix, e.g. libKF5Screen.so).
> 2. Another way of naming is a -qt5 suffix, e.g. libmarblewidget-qt5.so.
> 3. (probably some others?)
>
> Friedrikh said in [1] that using a KF5 prefix for all libraries will
> "blur the hint b
On 2015-04-20, Thomas Lübking wrote:
> You can apply that on really *anything* - the obvious (claimed) failure is
> "Qt breaks somehow Plasma" because either
> a) a client relied on undocumented behavior (client bug) or
> b) a foundation broke documented API/ABI/Behavior (foundation bug)
a) is h
On 2015-04-20, Albert Astals Cid wrote:
> Just state that there's no such long maintaince time for that package o=
> r just=20
> install the newer version of Qt. And yes again that probably goes again=
> st your=20
> rules, but it's your rules, so you can just improve them for everyone's=
>=20
> b
On 2015-04-20, Albert Astals Cid wrote:
> IMHO the duty of a distro is providing software to their users to use, =
> if the=20
> rules of the distro make providing software hard/impossible they need t=
> o be=20
> updated or these distros need to understand they will lose users to mor=
> e=20
> fl
On 2015-02-02, Martin Klapetek wrote:
> Another part that KDE Telepathy needs is KAccounts and we'd like
> to move that one too, probably to kde-runtime but there seems to be
> some disagreements of the purpose of kde-runtime. KAccounts is
I'm pretty sure that everything in kde-runtime is only fo
On 2014-04-29, Alexander Neundorf wrote:
> On Tuesday, April 29, 2014 21:00:57 Christoph Feck wrote:
>> I cannot remember we had these issues with the KDE3->KDE4 transition.
>
> Actually I think we had the same issues.
We did have the same issues. I pushed them thru with help of Allen and
David.
On 2013-12-18, Harald Sitter wrote:
> Thoughts on this? What do we do about it?
Tell ubuntu users to not use their distribution provided cmake because
ubuntu decided to break cmake by doing quick hacks instead of figuring
out how stuff works and then solve problems?
/Sune
ndows without dbus. not yet tested on other platforms
Thanks,
Sune Vuorela
ed on windows without dbus. not yet tested on other platforms
Thanks,
Sune Vuorela
files are
properly added, always returns false, so doesn't build with dbus. needs fixing
- Sune Vuorela
On Oct. 29, 2013, 10:27 p.m., Sune Vuorela wrote:
>
> ---
> This is an automatically generated e-mail. To reply,
575a6
tier2/kjobwidgets/src/config-kjobwidgets.h.cmake 35b64a2
tier2/kjobwidgets/tests/kjobtrackerstest.cpp 7a61407
Diff: http://git.reviewboard.kde.org/r/113503/diff/
Testing
---
build tested on windows without dbus. not yet tested on other platforms
Thanks,
Sune Vuorela
org/r/113479/diff/
Testing
---
Test suite passes
Thanks,
Sune Vuorela
hanks,
Sune Vuorela
t.cpp
a4484560735f9096ecdac26b3c539394602e0f31
tier1/kcoreaddons/src/lib/caching/kshareddatacache_win.cpp
cdc6536b56888a615e74960bf1b55fb12cc3e70d
Diff: http://git.reviewboard.kde.org/r/113479/diff/
Testing
---
Test suite passes
Thanks,
Sune Vuorela
On Oct. 11, 2013, 9:51 p.m., Mark Gaiser wrote:
> > We are here making a 'hole' for people to do 'bad things' that wasn't
> > possible in the past. I'm not sure we want that.
>
> Mark Gaiser wrote:
> Interesting.
> So that mean we simply can't use the new signal/slot syntax because of
#x27; for people to do 'bad things' that wasn't possible
in the past. I'm not sure we want that.
- Sune Vuorela
On Oct. 11, 2013, 5:59 p.m., Mark Gaiser wrote:
>
> ---
> This is an automatica
On 2013-09-25, Sebastian Kügler wrote:
> On Wednesday, September 25, 2013 17:51:41 Mark wrote:
>> Doesn't your naming proposal completely ruin the org.kde.* stuff? Up until
>> now i could fairly safely assume that all QML KDE imports where hidden
>> under org.kde.* but that isn't the case anymore
> On Sept. 24, 2013, 2:23 p.m., Sune Vuorela wrote:
> > tier1/kguiaddons/src/lib/colors/kcolorutils.cpp, line 42
> > <http://git.reviewboard.kde.org/r/112816/diff/1/?file=190519#file190519line42>
> >
> > My initial reaction is that it could return a bool we
ttp://git.reviewboard.kde.org/r/112816/#comment29951>
My initial reaction is that it could return a bool wether or not things
went okay, given there is a 'path that does nothing' in the code. Besides that,
everything looks great.
- Sune Vuorela
On Sept. 24, 2013, 2:19 p.m., Aurél
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112852/#review40588
---
Ship it!
Ship It!
- Sune Vuorela
On Sept. 21, 2013, 7:53
On 2013-07-14, Inge Wallin wrote:
> Here are some assumptions. Correct me if they are wrong:
> - KDE developers support the last relesed and *maybe* the second to last
> release with bugfixes.
> - Distributions have a release cycle of 6 months or longer.
> - Distributions pick their contents 2
On 2013-07-10, Àlex Fiestas wrote:
> I can't fight with distros, and I don't want to fight with them. If distros
> need .5 .6 and .200 so be it, just they will have to do them themselves (and
> I
> hope we can make the process smooth so they can actually do it).
>
> As has been said in this thr
On 2013-07-10, Aaron J. Seigo wrote:
>=3D=3D On scheduling mainenance releases
>
> in a longer 4 month cycle, i=E2=80=99d cut that to 8 weeks and keep jus=
> t the one=20
> update.
>
> this would ease the burdon on our release team (and by extension packag=
> ers)=20
> while also giving developer
On 2013-07-09, Sune Vuorela wrote:
> So. first one.
Second one
Release frequency.
We have a giant quality problem. Distros won't ship a .0 release to real
users (as opposed to testers/power users) and wait until there has been
a couple of bug fix releases. Until we ensure that our .0
On 2013-07-09, Àlex Fiestas wrote:
> If we keep copyright holders and licence, we can change the structure of the
> header, no?
We can.
/Sune
On 2013-07-08, Àlex Fiestas wrote:
I'm going to provide a handful of replies, each dealing with different
aspects of this - hopefully I will post them all over the next couple of
days. I will try to keep them short.
So. first one.
> Basically the idea is to cut testing time and compensate it by
On 2013-07-09, Vishesh Handa wrote:
> On Tue, Jul 9, 2013 at 6:08 PM, Harald Sitter 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
>
On 2013-06-20, Frank Reininghaus wrote:
> That would be great. I don't really know when will be the next time
> Thanks for your help and best regards,
Done.
Regards,
Sune
On 2013-06-20, Frank Reininghaus wrote:
> I admit that the current "solution" is an ugly hack. But it was never
> meant to be an "arms race". Please note that I proposed and
> implemented this at a time when Ivan still refused to acknowledge that
> there is a bug in his plugin at all. There was no
On 2013-06-19, Thomas Lübking wrote:
>> If I was a plugin developer here, I would of course think my plugin
>> should be enabled by default and thus in my ctor call
>> setEnabledByDefault(true)
>
> I would suggest to leave the path of plugin enabling as solution asap - it's
> not a solution at al
On 2013-06-17, Frank Reininghaus wrote:
> Yes, it can block for random reasons, and this is why making D-Bus
> calls in the code that is executed before the context menu is shown is
> unacceptable IMHO.
I agree with the problem. But the issue is to *fix* kactivities to not
do something insane. Th
On 2013-06-16, Albert Astals Cid wrote:
> So my path in a Plasma session is
> /usr/lib/x86_64-linux-gnu/qt4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
>
> This makes the QT_SELECT thing from qtchooser not work
> since if i do
> QT_SELECT=qt5 moc
>
On 2013-05-11, Friedrich W. H. Kossebau wrote:
> So, anyone with more clue than me WRT symbols from static libs and the
> Bsymbolic-functions linker flag who could tell if that indeed should fix such
> problems if code from the same static lib is arriving multiple times in the
> same process vi
On 2013-04-29, Milian Wolff wrote:
> I do wonder though why QString has both, a shared_empty and a shared_null
> object. A single one should suffice for most objects, no?
I'm pretty sure this is because QString can be empty and not null.
e.g. the difference between QString() the empty string.
On 2012-12-25, Sven Brauch wrote:
> Also, I'm still not sure what exactly concerns you about security and
> maintenance. Problems I see include increased build time, and
> maintenance efforts for me personally in updating the fork, but none
> really seem fatal. Can you elaborate a bit about which
On 2012-12-01, Del wrote:
> I just realised that System Settings no longer has the kcmsambaconf module
> for
> configuring Samba. The only trace I found of the decision was a Debian bug
> report:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691634
It is available. it can be reached thru
On 2012-10-13, Albert Astals Cid wrote:
> Back when I moved ktouchpadenabler to extragear-base Christoph mentioned he'd
> like to see it in kdebase[1], we don't have a kdebase anymore though.
>
> Anyway i'd like to move it to a more central place, I guess kde-workspace
> would be the place for t
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/106780/#review20172
---
Ship it!
Ship It!
- Sune Vuorela
On Oct. 10, 2012, 1:20
On 2012-09-20, David Faure wrote:
> We really need a FHS addition for libexec.
not really. the libexec executables is in general a implementation
detail of the given library.
We have the rare case in KDE that we actually call other libraries'
executables, which is a different thing, and one I ha
On 2012-09-20, Kevin Krammer wrote:
> Do you mean $PREFIX/libexec, where $PREFIX will often be /usr (for=20
> distribution packages)?
that only works in redhat/fedora land. In other distributiotns, like
debian and ubuntu, libexec is placed in directories under
prefix/libdir/libraryname/ - e.g.
On 2012-09-20, Kevin Krammer wrote:
> Agreed. It is important, however, to remember that some of those (e.g.=20
> akonadiserver, akonadi_control) are not KDE programs and can therefore not =
> be=20
> in a KDE specific libexec location but have to go into a standard (FHS or=20
> freedesktop.org) l
On 2012-08-30, David Faure wrote:
> I think this is a "belt and suspenders" kind of thing (extra precaution)...
> in
> theory it's not necessary, kded will detect new desktop files on kde startup,
> or during the upgrade process if KDE is already running.
>
> I wonder if Waldo added that (long
On 2012-08-29, Albert Astals Cid wrote:
> Yes, this is what we did.
>
> Let me rephrase the question.
>
> Is what we did the correct thing? (I'm not saying it is or it is not, just
> that i have to tag 4.9.1 tomorrow and i want to know if I have to increase
> that or not).
having them saying {4
On 2012-08-22, David Edmundson wrote:
> release. This isn't a decision forced by Canonical, they just think
> it's better, though obviously it helps that the backend is already
> tested on Ubuntu. Other distributions have also expressed an interest,
Is LightDM a canonical project? one that is cov
On 2012-06-12, Sebastian Trüg wrote:
> I do not have much time. But the real problem is that I am not sure
> where to look. It has to do with my own implementation of unix socket
> communication. Someone with experience in that area might want to review
> the *Socket* classes in soprano/client.
On 2012-06-12, Vishesh Handa wrote:
> --bcaec554d60626569204c246cba9
> Content-Type: text/plain; charset=ISO-8859-1
>
> Yeah. So Nepomuk is the cause of the problems -
>
> Here our our options -
>
> 1. I revert Sebastian's commits in kdelibs. This should fix the issue, but
> we would need to reint
On 2012-06-11, Sebastian Kügler wrote:
> I'd consider that a bug in your packaging. There's no absolute requirement of
> an app for a specific version of kdelibs. If your packages need that, you
> should probably fix them. The decoupling of libs and apps, and especially the
> modularization of
n 05/17/2012 09:19 PM, Sune Vuorela wrote:
>> On 2012-05-17, Vishesh Handa wrote:
>>> @Packagers: We will not be maintaining binary compatibility in
>>> nepomuk-core. At least not for KDE 4.10. We still need to break a lot of
>>> things.
>>
>> NACK.
>>
>> this is a completely no go.
>>
>> /Sune
>>
>>
>
On 2012-05-17, Vishesh Handa wrote:
> @Packagers: We will not be maintaining binary compatibility in
> nepomuk-core. At least not for KDE 4.10. We still need to break a lot of
> things.
NACK.
this is a completely no go.
/Sune
On 2012-05-07, Vishesh Handa wrote:
> I'm not okay with applications having to stick with the old faulty APIs
I'm not okay with a api or abi break in kdelibs.
/Sune
On 2012-05-07, Vishesh Handa wrote:
> Right.
>
> We could maintain BC and SC by not touching the kdelibs nepomuk, and just
> making nepomuk-core a dependency of kdelibs. But that would result in both
> nepomuk-core and kdelibs installing the same headers.
what happens if both libraries are loaded
On 2012-04-28, George Kiagiadakis wrote:
> No, the classes that wrap GObjects do not need a d-pointer. All the
> calls are forwarded to the underlying GObject and if for any reason we
> ever need to save extra data on the wrapper class (which is highly
> unlikely), we should use the GObject qdata
On 2012-04-06, Thiago Macieira wrote:
>
> --nextPart4816581.q9J4AAnfuU
> Content-Transfer-Encoding: 7Bit
> Content-Type: text/plain; charset="us-ascii"
>
> On sexta-feira, 6 de abril de 2012 01.14.34, David Edmundson wrote:
>> > I don't think so. The classes are likely not to be exported.
>>
>> W
On 2012-03-22, Daniel Nicoletti wrote:
> people draw API they have this in mind and we don't need a whole new Qt just
> to
> introduce a new feature, easy solution: QApplication::setColorCorrected(true);
That's crap API thoug.h
QApplication::setBehaveSane(true);
QApplication::setPleaseDontCrash
On 2012-03-14, Lamarque V. Souza wrote:
> I should stop working in Plasma NM then since for distributions that
> ships Gnome as default desktop nm-applet is the standard.
erm. you are aware that colord better can be compared to NetworkManager
than to Plasma NM ?
/Sune
On 2012-03-14, Lamarque V. Souza wrote:
> You are talking as if colord is the default standard and well used in
> KDE and then out of a suden comes oyranoes trying to replace it. Colord is
> not
> wide used in KDE and since oyranos includes a wider feature set I guess it is
No. colord s
On 2012-03-14, Boudewijn Rempt wrote:
> It's easy enough to package -- the opensuse packages I use work perfectly
> fine, so I cannot imagine that there are any real and relevant problems
> for other distributions.
Sure it can be done. but it is just useless churn if it doesn't really
provide a
On 2012-03-14, Daniel Nicoletti wrote:
>> Request:
>
>> After working on KolorManager and Oyranos in the past months for the last
>> Oyranos-0.4.0 release, we feel the stack is ready to review for inclusion
>> into
>> KDE.
>> KolorManager resides currently in Playground/Graphics:
>> http://quic
On 2012-02-22, David Faure wrote:
> 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 abuses them". This is also what we do for SVN/GIT, so why don't we do
> this for bugzilla? Presu
On 2012-02-24, Hugo Pereira Da Costa 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 correct.
Whattabout just linking liboxygenstyle static into the oxygen style?
Prob
On 2011-10-03, Allen Winter wrote:
> On Monday 03 October 2011 5:04:45 AM Albert Astals Cid wrote:
>> A Dilluns, 3 d'octubre de 2011, Alexander Neundorf vàreu escriure:
>> > On Monday 03 October 2011, Allen Winter wrote:
>> > > Howdy,
>> > >
>> > > A lot of CMakeLists.txt use the ${GENERIC_LIB_VE
On 2011-09-30, Albert Astals Cid wrote:
> A Divendres, 30 de setembre de 2011, Sebastian Trüg vàreu escriure:
>> Hi lists,
>>
>> with frameworks in the building and Nepomuk probably going that
>> direction already for 4.8 I would like to clean up a bit. One of these
>> cleanup tasks targets the S
On 2011-09-22, Albert Astals Cid wrote:
> This means that as a user if the developer decides to use a "Popup" I can no
> longer configure the application to do nothing? Or to play a sound?
No. It just means that the responsibility is handed over to the
application developer if they want to offer
On 2011-09-22, Sune Vuorela wrote:
...and of course, bits of my drafts fell out when doing the last reorder
of things.
> Hi
>
> I'm considering doing some work on the knotify-stuff for the kde
> frameworks.
> This involves the KNotification class and the KNotify daemon a
Hi
I'm considering doing some work on the knotify-stuff for the kde
frameworks.
This involves the KNotification class and the KNotify daemon and related
classes.
I started hacking a bit on it in Randa, but have ended up scratchig my
work and starting over. http://pusling.com/blog/?p=200
Current
On Thursday 14 July 2011 03:42:01 Michael Jansen wrote:
> On Thursday 14 July 2011 10:49:50 Ian Wadham wrote:
> > On 14/07/2011, at 5:16 AM, Alexander Neundorf wrote:
> > > What do you think of this ?
> > > More wishes ?
> > > Should it do it in a different way ?
> >
> > Very nice. I especially l
On 2011-07-04, Albert Astals Cid wrote:
> --Boundary-01=_YFgEOebgzUxkqvf
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> A Monday, July 04, 2011, Dawit A va escriure:
>> The following files all contain set but unused variables:
>>
>> snip
>>
>> Unlike the
> (Updated June 20, 2011, 10:58 p.m.)
>
>
> Review request for kdelibs and Sune Vuorela.
>
>
> Summary
> ---
>
> This patch adds the missing checks for xmllint. xmllint is a de facto
> dependency for kdelibs, a fresh rebuild fails without it (thanks to
On 2011-06-21, Rolf Eike Beer wrote:
> So if it is a double you are truncating it to a float (on ARM). I don't know
> if
> that is intentional.
Given the api is taking qreal's, I think it is intentional.
/Sune
On 2011-06-04, ?? ?? wrote:
> Hello. I am using Gentoo on the Beagleboard-Xm.
> When I try to compile kde-4.6.80, I stoped on the grantlee build phase.
> This is a full log.
> http://paste.ubuntu.com/618234
/var/tmp/portage/dev-libs/grantlee-0.1.8/work/grantlee-0.1.8/t
On 2011-05-21, Dirk Mueller wrote:
> Is the previous rule no longer valid? otherwise, how to deal with this
> situation? Move plasma to experimental? remove the dependency again?
That rule is still valid.
And. how is one supposed to be building kdelibs if it requires
kdelibs-experimental which
On 2011-05-17, Steven Sroka wrote:
> Exactly. Do I hear KDE5? :)
if you do hear it, it will still require a clipboard manager in the
workspace as long as we are targetting X11...
/Sune
On 2011-05-17, Sebastian Trüg wrote:
> KDE-PIM < 4.7 is another problem as it does not build against kdelibs
> 4.7. But then again: who does that? I know that is not a great argument,
I'm pretty sure several distributions might want to push kdelibs +
workspaces and such in newer versions to users
On 2011-05-16, Steven Sroka wrote:
>>On 16 May 2011 04:24, Andreas Pakulat wrote:
>> On 15.05.11 22:32:21, Steven Sroka wrote:
>>> I'm interested if anyone knows why kdebase-workspace depends on
>>> Klipper? I love how various KDE components are very modular, but for a
>>> while now that weird de
On 2011-02-15, Sune Vuorela wrote:
> Hi peoples
>
> I have added prison (git clone kde:prison) to kdereview, targetting
> kdesupport.
moved.
/Sune
On 2011-02-15, Sune Vuorela wrote:
>> Are there generated docs available somewhere for easier API review?
>
> Currently not, but I can do that later.
http://alioth.debian.org/~pusling-guest/prison/apidocs/html/
/Sune
1 - 100 of 109 matches
Mail list logo
