KAppTemplate and KDevelop 5.x are not coinstallable

[Kevin Funk]

On Thursday, January 07, 2016 02:46:43 PM Milian Wolff wrote:
> On Donnerstag, 7. Januar 2016 14:06:47 CET Simon Wächter wrote:
> > Hi Alexander & Kevin
> > 
> > Thank you for the hint. Strange that we didn't notice that earlier

Because we didn't install that particular template until a while ago (we 
forgot to enable it)

> > (Also that no package system complained about that file conflict). I
> > recommend that we delete the qmake template in KAppTemplate and keep
> > the one in KDevelop. KDevelop also provides other pure Qt templates.

Okay.

Currently we have the following kdevtemplates in kapptemplate.git:

```
./src/templates/QML/qt5-qml2/qt5-qml2.kdevtemplate
./src/templates/C++/qmake_qt4guiapp/qmake_qt4guiapp.kdevtemplate
./src/templates/C++/cmake_qt5guiapp/cmake_qt5guiapp.kdevtemplate
^ move to kdevelop.git / merge?

./src/templates/C++/akonadiresource/akonadiresource.kdevtemplate
./src/templates/C++/runner/runner.kdevtemplate
./src/templates/C++/kapp4-qml/kapp4-qml.kdevtemplate
./src/templates/C++/kde-simple/kde-simple.kdevtemplate
./src/templates/C++/kpartapp/kpartapp.kdevtemplate
./src/templates/C++/akonadiserializer/akonadiserializer.kdevtemplate
./src/templates/C++/kde-frameworks5/kde-frameworks5.kdevtemplate
./src/templates/C++/ktexteditor/ktexteditor.kdevtemplate
./src/templates/C++/konqplugin/konqplugin.kdevtemplate
./src/templates/C++/kde-frameworks5-simple/kde-frameworks5-simple.kdevtemplate
```

Makes sense?

@Simon: Would you be willing to do the move? You know both kdevelop & 
kapptemplate.

That'd be awesome.

Cheers,
Kevin

> > 
> > With review request 126185 we now have a global macro and I should
> > port the CMake code. My personal idea for the future is that every
> > library/framework provides an own set of templates (Based on the new
> > kdetemplate_add_app_templates macro) and we move all KAppTemplate (and
> > KDevelop) templates to the correct project/repository. With this
> > approach we don't have to maintain templates (or even programming
> > languages like Python/Ruby) which we don't know/good enough, for
> > example the old KOffice, KRunnter etc. Every project should be
> > responsible for their own templates - they know them.
> > 
> > Any thoughts about this idea?
> 
> Sounds like a good idea to me!

-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160107/74c30a11/attachment.sig>