[Kde-pim] Move FindKdeSubversion to *libs.

[Allen Winter]

On Sunday 10 February 2008 16:34:01 Andras Mantia wrote:
> On Sunday 10 February 2008, Allen Winter wrote:
> > I could imagine this being useful for konqueror, but I'm not sure
> > if we are permitted to put new CMake modules into kdelibs.
>
> It is the second time I read this. Why wouldn't it be allowed? If your
> application is developed for a KDE version which does not yet have the
> check, you include a copy. If you care only about running with the
> latest KDE release, you use the kdelibs version. Unless there are
> *technical* reasons not to do it (like you cannot have the same module
> both in kdelibs and as a local copy), I see no reason to disallow adding
> new checks and cmake modules to kdelibs.
>

We, kdepim, very much want to continue building against kdelibs 4.0.
Which means we need to keep a copy.  I'm fine with that.

So this means we can add content into
http://techbase.kde.org/index.php?title=Policies/CMake_and_Source_Compatibility#What_changes_are_possible.3F
bullet 1. New modules can be added

Yes, new cmake modules can be added, but copies of the modules must also be retained
inside each individual KDE package (module) that uses those modules.

Alex ????