Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-05-10 Thread Alexander Neundorf
On Tuesday 27 April 2010, Alexander Neundorf wrote: > On Tuesday 27 April 2010, Kevin Ottens wrote: > > On Monday 12 April 2010 18:51:41 Alexander Neundorf wrote: > > > On Monday 12 April 2010, Kevin Ottens wrote: > > > > On Saturday 10 April 2010 19:34:14 Alexander Neundorf wrote: > > > > > Doesn'

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-28 Thread Kevin Ottens
On Wednesday 28 April 2010 21:37:02 Alexander Neundorf wrote: > On Wednesday 28 April 2010, Kevin Ottens wrote: > > On Tuesday 27 April 2010 22:02:33 Alexander Neundorf wrote: > > 3) The platform profile definition has to be processed as early as > > possible (in particular before the add_subdirect

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-28 Thread Alexander Neundorf
On Wednesday 28 April 2010, Kevin Ottens wrote: > On Tuesday 27 April 2010 22:02:33 Alexander Neundorf wrote: > > kdelibs_cmake_profiles.patch: > > Looks good, but I would put the information not in a separate > > KDEPlatformProfile.cmake file, but just in the already existing > > KDELibsDependenci

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-28 Thread Alexander Neundorf
On Wednesday 28 April 2010, Marco Martin wrote: > On 4/27/10, Ian Lawrence wrote: > > Hi > > > > > kdelibs_cmake_profiles.patch: > > > > It might be worth mentioning the effect that this patch could have on > > downstream. Three build runs, tripling the build time. I am > > uncomfortable with

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-28 Thread Kevin Ottens
On Tuesday 27 April 2010 22:02:33 Alexander Neundorf wrote: > kdelibs_cmake_profiles.patch: > Looks good, but I would put the information not in a separate > KDEPlatformProfile.cmake file, but just in the already existing > KDELibsDependencies.cmake file. > > (if you have a look at that file you'l

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-27 Thread Alexander Neundorf
On Tuesday 27 April 2010, Kevin Ottens wrote: > On Monday 12 April 2010 18:51:41 Alexander Neundorf wrote: > > On Monday 12 April 2010, Kevin Ottens wrote: > > > On Saturday 10 April 2010 19:34:14 Alexander Neundorf wrote: > > > > Doesn't look too bad, but I wouldn't commit it before there is > > >

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-26 Thread Kevin Ottens
On Monday 12 April 2010 18:51:41 Alexander Neundorf wrote: > On Monday 12 April 2010, Kevin Ottens wrote: > > On Saturday 10 April 2010 19:34:14 Alexander Neundorf wrote: > > > Doesn't look too bad, but I wouldn't commit it before there is > > > something which also uses this. > > > > Well, it's c

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-15 Thread Alexander Neundorf
On Thursday 15 April 2010, Kevin Ottens wrote: > On Monday 12 April 2010 18:51:41 Alexander Neundorf wrote: > > How about putting it in together with the first use of it ? > > OK, fair enough. We'll probably make a separate commit for it though. > > > I'd also wait for a conclusion of the discussio

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-15 Thread Kevin Ottens
On Monday 12 April 2010 18:51:41 Alexander Neundorf wrote: > How about putting it in together with the first use of it ? OK, fair enough. We'll probably make a separate commit for it though. > I'd also wait for a conclusion of the discussion on k-c-d. Of course. Although I'd say it's reaching it

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-13 Thread Kevin Ottens
On Saturday 10 April 2010 19:34:14 Alexander Neundorf wrote: > Doesn't look too bad, but I wouldn't commit it before there is something > which also uses this. Well, it's chicken and egg problem. We kind need it in order to start the efforts of cutting deps and so on which will use the content of

Re: [Kde-maemo] kdelibs modularizing (kde-mobile)

2010-04-12 Thread Alexander Neundorf
On Monday 12 April 2010, Kevin Ottens wrote: > On Saturday 10 April 2010 19:34:14 Alexander Neundorf wrote: > > Doesn't look too bad, but I wouldn't commit it before there is something > > which also uses this. > > Well, it's chicken and egg problem. We kind need it in order to start the > efforts