Merging "generic project manager" and "custom buildsystem"

Milian Wolff mail at milianw.de
Wed Jun 25 14:40:12 UTC 2014


On Wednesday 25 June 2014 15:29:35 Aleix Pol wrote:
> On Sun, Jun 22, 2014 at 1:36 PM, Milian Wolff <mail at milianw.de> wrote:
> > Hey all,
> > 
> > a user just noticed that the custom buildsystem KCM was shown in the
> > project
> > configuration dialog. I'll try to find out why that is and ensure its not
> > being show there.
> > 
> > But it did made me wonder: Do we want to bother a user with this decision?
> > Couldn't we just make the "custom buildsystem" our "generic project
> > manager"
> > and be done with it?
> > 
> > The generic manager is mostly useful for simple script projects and
> > similar,
> > which are also nicely handled by the custom build system with an empty
> > configuration - no?
> > 
> > Furthermore, once a script project becomes a bit more involved, having a
> > way
> > to run a script to deploy the project somewhere or similar might be nice
> > to
> > have, and with the custom buildsystem you'd get that for free, no?
> > 
> > Opinions?
>
> I like the idea. Can we just consider generic project manager deprecated
> and only go with Custom BuildSystem?

Yes, but we'll have to move the CBS into kdevplatform. Furthermore, I think I 
prefer "generic project manager" over the "custom buildsystem" name.

So we'd merge the latter into the former, thereby essentially deprecating it.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de


More information about the KDevelop-devel mailing list