topic request for next week's meeting: build requirements for kf5

[Alexander Neundorf]

On Tuesday 21 May 2013, Aaron J. Seigo wrote:
> Hi,
> 
> Post 4.11, we will be encouraging as many people working on Workspace stuff
> as possible to move over to KF5 (inc plasma-framework). It will be
> critical to have a clear, (accurately) documented and reliable build (and
> update) recipe.
> 
> Given the feedback in the last few weeks on building kf5, it is apparent
> that right now we lack that. So I would like to propose this as a topic
> for next week's Wednesday KF5 irc meeting.
> 
> Specifically, I'd like to see if we can find consensus on:
> 
> * cmake requirements (version of cmake, 
> * e-c-m; how to update those in future

My take:

cmake: as long as kf5 has not been released yet, require at most the latest 
released stable version. Announce at least a day in advance when the new 
version will be required.

e-c-m: what I do: if a new feature is added to e-c-m, I increase the version 
number. When this feature is used somewhere, I require that new version number 
there. Usually I also send an email to kde-frameworks which announces that.

Is e-c-m different than all the other git modules we (will) have ?

We can also stay with "most recent git", but I would prefer to be notified if 
some of my dependencies are too old and that I need to update them, instead of 
a failing cmake or build, and then having to update all git repos this project 
depends on just in case (there will be many in the future).

> * qt5 (with a clear recipe that works, including for updating)

Yes, please :-)

Alex