please make it easier to hack on frameworks

Alexander Neundorf neundorf at kde.org
Mon Apr 29 16:46:11 UTC 2013


On Monday 29 April 2013, Kevin Ottens wrote:
> On Monday 29 April 2013 18:13:59 Alexander Neundorf wrote:
> > On Monday 29 April 2013, Aaron J. Seigo wrote:
> > > hi ...
> > > 
> > > today i am unable to work on plasma-frameworks. this is because i am
> > > currently unable to compile the frameworks branch of kdelibs. in turn,
> > > this is because i do not have a recent enough version of cmake.
> > > 
> > > the cmake version required is 2.8.10.20130411. this isn't even a
> > > release version of cmake, but a dated snapshot! i am left with the
> > > option of moving to cmake from git (something i really would like to
> > > avoid) or not working on plasma-frameworks (which is not really an
> > > option for me).
> > > 
> > > i am sure there was a good reason to move to this new version of cmake.
> > > i am also sure that requiring devel versions of build tools to work on
> > > frameworks limits the people who can and will work on it.
> > > 
> > > would it be possible for someone who feels reponsible for frameworks 5
> > > to institute some more developer-friendly requirements here?
> > 
> > I am all for requiring only released versions of cmake.
> > Or at least announcing it when an update is required.
> > But it seemed to be the majority opinion that this is not necessary in
> > kf5.
> 
> Well it's been necessary at some point because you needed to make fast
> paced changes. I didn't expect that habit to stick though. When is the
> next release of cmake planned? If we could stick to that one for a while
> that would be nice.
> 
> Once it's released we should not depend on unreleased cmake version anymore
> IMO.

cmake 2.8.11 is about to be released very soon, maybe two weeks or so.
If I followed Stephens work correctly currently we can't go back to 2.8.10, 
right ?

Alex


More information about the Kde-frameworks-devel mailing list