KTextEditor & Frameworks question

[David Faure]

On Saturday 04 January 2014 22:40:13 Christoph Cullmann wrote:
> > On Saturday 04 January 2014 19:40:46 Christoph Cullmann wrote:
> > > What would be required to have the ktexteditor stuff be "frameworks"
> > > ready?
> > 
> > Using all the cmake stuff from other frameworks ;)
> > 
> > I just updated and moved the framework template we had in kdelibs to
> > kdeexamples/framework-template. You can use this to generate the entire
> > directory structure if you want.
> 
> Ok,
> 
> that shall be not really a problem, given I have already the autotests in
> the right dir and only ktexteditor => src is needed.

This is about the contents of the CMakeLists.txt files too.
You should port to ecm_generate_headers if you don't use it yet (you can use my
script for that, kde-dev-scripts/kf5/install_forwarding_headers.pl)
and compare the cmake stuff with e.g. kcoreaddons or the template.

> Still, what would be the appropriate way to split the kate.git without
> loosing the history.

Do it just like we did for kdelibs: new repo, old history available via grafting.
See kde-dev-scripts/frameworks/split_out_frameworks.sh
(change the "for" loop, obviously - you don't need a loop at all, if you have
only one repo to split out). Maybe don't even run the script, just run the commands
one by one, to adapt them to your directory structure.

Once you have the clean new repo, you'll need to talk to sysadmin for uploading it.

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5