Re: Separating everything ?

Hi Patrick, 2013/2/8 Patrick Spendrin: > Am 07.02.2013 23:32, schrieb Frank Reininghaus: > ... > > Since I am reading this thread by chance, I might as well reply. > > One of the reasons of splitting kdelibs into separate repositories is to > simplify the usage of single modules. > From the perspe

Re: Separating everything ?

On Thursday 7 February 2013 23:32:12 Frank Reininghaus wrote: > If, however, a user decides to clone the repository and build from > source or, even better, start contributing, I seriously doubt that > cloning one frameworks repository and then cd'ing to the interesting > framework would be perceiv

Re: Problems with ECM / FindKDE4Internal and plasma-framework

On Fri, Feb 8, 2013 at 11:16 AM, Alexander Neundorf wrote: > On Thursday 07 February 2013, Ben Cooksley wrote: >> On Fri, Feb 8, 2013 at 6:38 AM, Alexander Neundorf wrote: >> > On Thursday 07 February 2013, Ben Cooksley wrote: >> >> On Thu, Feb 7, 2013 at 7:34 AM, Alexander Neundorf > wrote: >>

Re: Review Request 108845: add support for SSSE3 and SSE4.2 in cpufeatures and for msvc

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108845/ --- (Updated Feb. 8, 2013, 1:09 a.m.) Review request for KDE Frameworks, kdeli

Re: Separating everything ?

Am 07.02.2013 23:32, schrieb Frank Reininghaus: ... Since I am reading this thread by chance, I might as well reply. One of the reasons of splitting kdelibs into separate repositories is to simplify the usage of single modules. >From the perspective of a full *KDE* desktop, there is no problem in

Re: New "official" way how to use an installed kdelibs from the frameworks branch

On Friday 08 February 2013, Alexander Neundorf wrote: > Hi, > > after looking at the current plasma-framework buildsystem I worked a bit on > the kdelibs and plasma buildsystem, and there is now a somewhat sane way to > use an installed kdelibs from the frameworks branch. > > So, compared to kdel

New "official" way how to use an installed kdelibs from the frameworks branch

Hi, after looking at the current plasma-framework buildsystem I worked a bit on the kdelibs and plasma buildsystem, and there is now a somewhat sane way to use an installed kdelibs from the frameworks branch. So, compared to kdelibs before, now FindKDE4Internal.cmake is no longer installed. In

Re: Review Request 105868: KF5 - Q_OS_* not defined

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105868/#review26922 --- This review has been submitted with commit b5767214c579a69d0c6

Re: Separating everything ?

Hi, 2013/2/7 Kevin Ottens: > On Thursday 7 February 2013 16:09:51 Frank Reininghaus wrote: >> Is there anything obvious that I'm overlooking? One could argue that >> separate repositories make it easier for non-KDE people to contribute >> to one particular framework. > > It's not only contributing

Re: Problems with ECM / FindKDE4Internal and plasma-framework

On Thursday 07 February 2013, Ben Cooksley wrote: > On Fri, Feb 8, 2013 at 6:38 AM, Alexander Neundorf wrote: > > On Thursday 07 February 2013, Ben Cooksley wrote: > >> On Thu, Feb 7, 2013 at 7:34 AM, Alexander Neundorf wrote: > >> > On Tuesday 05 February 2013, Alexander Neundorf wrote: > >> >>

Re: Review Request 106501: Port some uses of KUrl to QUrl

> On Feb. 7, 2013, 9:08 p.m., Albert Astals Cid wrote: > > I see this has a shit it but marked as uncommited. Was it commited and you > > forgot to close the request or is still uncommited? Yeah. I should shit this at some point :) - Kevin ---

Re: Review Request 106501: Port some uses of KUrl to QUrl

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/106501/#review26876 --- I see this has a shit it but marked as uncommited. Was it commi

Re: Problems with ECM / FindKDE4Internal and plasma-framework

On Fri, Feb 8, 2013 at 6:38 AM, Alexander Neundorf wrote: > On Thursday 07 February 2013, Ben Cooksley wrote: >> On Thu, Feb 7, 2013 at 7:34 AM, Alexander Neundorf wrote: >> > On Tuesday 05 February 2013, Alexander Neundorf wrote: >> >> On Monday 04 February 2013, Ben Cooksley wrote: >> >> > Hi a

Re: Separating everything ?

On Thursday 07 February 2013 21:11:02 Alexander Neundorf wrote: > On Thursday 07 February 2013, Kevin Ottens wrote: > > On Thursday 7 February 2013 16:09:51 Frank Reininghaus wrote: > > > Is there anything obvious that I'm overlooking? One could argue that > > > separate repositories make it easier

Re: Separating everything ?

On Thursday 07 February 2013, Kevin Ottens wrote: > On Thursday 7 February 2013 16:09:51 Frank Reininghaus wrote: > > Is there anything obvious that I'm overlooking? One could argue that > > separate repositories make it easier for non-KDE people to contribute > > to one particular framework. > >

Re: Separating everything ?

On Thursday 7 February 2013 16:09:51 Frank Reininghaus wrote: > Is there anything obvious that I'm overlooking? One could argue that > separate repositories make it easier for non-KDE people to contribute > to one particular framework. It's not only contributing but also using. It's almost more im

Re: plasma-framework buildsystem

On Thursday 07 February 2013, you wrote: > On Thursday 07 February 2013, Marco Martin wrote: > > On Thursday 07 February 2013, Alexander Neundorf wrote: > > > Hi Marco, > > > > hi alex > > > > > I just had a look at the plasma-framework buildsystem, it is quite > > > messy. > > > > yep :/ > > >

Re: plasma-framework buildsystem

On Thursday 07 February 2013, Marco Martin wrote: > On Thursday 07 February 2013, Alexander Neundorf wrote: > > Hi Marco, > > hi alex > > > I just had a look at the plasma-framework buildsystem, it is quite messy. > > yep :/ > > > Which parts of kdelibs do you use in plasma-frameworks ? > > Bet

Re: plasma-framework buildsystem

On Thursday 07 February 2013, Alexander Neundorf wrote: > Hi Marco, hi alex > I just had a look at the plasma-framework buildsystem, it is quite messy. yep :/ > Which parts of kdelibs do you use in plasma-frameworks ? > Better search for those and skip FindKDE4Internal.cmake. > Compiler setting

Re: Problems with ECM / FindKDE4Internal and plasma-framework

On Thursday 07 February 2013, Stephen Kelly wrote: > Alexander Neundorf wrote: > > OTOH, AFAIK currently at least I am not aware of what the official way of > > using the frameworks branch of kdelibs is. > > > > Do we have an official way ? > > When I built a bunch of kde repos using kf5, I think

plasma-framework buildsystem

Hi Marco, I just had a look at the plasma-framework buildsystem, it is quite messy. Which parts of kdelibs do you use in plasma-frameworks ? Better search for those and skip FindKDE4Internal.cmake. Compiler settings etc. you can get from KF5, see e.g. kdelibs/tier1/karchive/CMakeLists.txt. I'm

Re: Problems with ECM / FindKDE4Internal and plasma-framework

On Thursday 07 February 2013, Ben Cooksley wrote: > On Thu, Feb 7, 2013 at 7:34 AM, Alexander Neundorf wrote: > > On Tuesday 05 February 2013, Alexander Neundorf wrote: > >> On Monday 04 February 2013, Ben Cooksley wrote: > >> > Hi all, > >> > > >> > Currently the KDE CI system is unable to build

Re: Separating everything ?

On Wednesday 06 February 2013, Kevin Ottens wrote: ... > > I don't know if the tiers are the right 'tectonic plates' to base that on > > though. > > Definitely not IMO, that sounds rather artificial to me. > > > I expect it will become more clear how we can group them when we have > > them split

Jenkins build is back to stable : kdelibs_frameworks_qt5 #359

See ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Separating everything ?

Hi, 2013/2/6 Alexander Neundorf: > Hi, > > at Kevin's talk about KDE frameworks at FOSDEM last weekend, one guy from the > audience asked why he should not use all KDE libs if he decides to use one > already... > > This got me thinking. > Obviously, dragging in everything is what we want to avoid.