policy for adding cmake modules to kdelibs/cmake/modules/

[Allen Winter]

On Friday 09 January 2009 1:33:46 pm Alexander Neundorf wrote:
> Hi,
>
> all cmake modules which are in kdelibs/cmake/modules/ are installed on
> "make install", and so form part of the public interface of kdelibs, i.e.
> we must keep source compatibility for them. This is a not negligible
> maintainance effort.
> Currently usually modules are added if they are used by at least two
> modules. These are quite many, i.e. for KDE 4.3 already 2 new ones again.
>
> I would suggest to increase the threshold to 3 users of a module.
> As long as there are only 2 users, both apps/modules can keep a copy of the
> module (so at least only one module has to be kept in sync manually).
> That's not really nice, but I'm afraid adding more and more modules to
> kdelibs and keeping them compatible may become a maintainance problem in
> the long term. (actually that's the same reason why new modules are only
> added to cmake itself if somebody offers to maintain it).
>
> What do you think ?
>
We sure have  a lot, don't we.
~90 FindFoo.cmake's in kdelibs

I'm not sure I like your proposal, however. .. goes against our way of doing things.
One day, all packages will provide their own FooConfig.cmake and then we won't
have any individual maintenance at all :)