On Thu, Nov 19, 2015 at 5:50 PM, Marco Martin <notm...@gmail.com> wrote: > On Thursday 19 November 2015, Sebastian Kügler wrote: >> On Wednesday, November 18, 2015 11:37:16 AM Marco Martin wrote: >> > On Monday 16 November 2015, Sebastian Kügler wrote: >> > > > yes, makes sense, most important is to have them in places harder to >> > > > forget about >> > > >> > > If in plasma-framework, it would kind of fit in with all the example >> > > plasmoid code. Not sure if that, or plasma-sdk, both make sense to me, >> > > perhaps plasma- sdk a bit more, even. >> > >> > sooo, plasma-sdk or plasma-framework? is the same for me, i have them >> > ready, just to push wherever >> > >> > the argument for plasma-framework to me is *if* other frameworks are >> > going to have their own templates in their repos as well >> >> Let's go for plasma-framework. > > ok then. > now, another technical question (looking mostly at Aleix as ide-related tools > master:p) templates right now are installed by a quite complicated cmake macro > that is in kapptemplate as well (it creates a tarball from the sources and > then installs the tarball) > so.. > since frameworks can't depend from kapptemplate for said cmake macro... > > if many frameworks will end up having project templates, that should go in > extra-cmake-modules? if so and is something of global frameworks interest i > can try to go for such a global macro before pushing the rest > > -- > Marco Martin
Yes, I think it's the best way to go: to get the macro itself in extra-cmake-modules. Adding as CC current maintainer of KAppTemplate. It's with him that we discussed that. If you want, before working on the patch, you can send an e-mail to frameworks to agree to go at once somehow. Cheers! Aleix _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
