Kevin Ottens wrote: >> That could obsolete ecm_mark_as_test etc. > > Sure, I don't see how that's different from classes or methods we have in > our libraries at the moment which will get obsoleted by some later Qt > version. With that line of thinking we'd never release. > > Just mark modules which gets obsoleted as deprecated... Or I'm missing > something?
/shrug/ It's your call. My opinion is that releasing a fork of something that's already in cmake master is not a good idea. Will the CMake version override the fork when it is released? That file will be in a CMake release early next year I guess. Sure, that's after you want to release karchive and threadweaver, but before everything else. Thanks, Steve. _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
