KAppTemplate and KDevelop 5.x are not coinstallable

Milian Wolff mail at milianw.de
Thu Jan 7 13:46:43 UTC 2016


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
> (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.
> 
> 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!

-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- 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/a5d8ddc5/attachment.sig>


More information about the KDevelop-devel mailing list