kdesupport changes

[Allen Winter]

On Wednesday 10 September 2008 19:06:36 you wrote:
> On Sunday 07 September 2008, Allen Winter wrote:
> 
> > > development branch of Eigen be a place where we can experiment and
> > > break stuff without affecting our users. So, I support your plan.
> > There seems to be another set of kdesupport developers who
> > rely on the KDE folks to help test their stuff in-progress, just
> > like any other KDE code.  Hence the push-back on this idea.
> 
> Pardon, I've not seen any pushback on this mailing list.

The pushback happened on k-c-d.
I think that's a valid list for us to discuss these types of issues.

> can we ask that set of kdesupport developers to voice their concerns and their
> suggestion on this mailing list as part of the discusison so that we can move it
> forward, instead of deciding something and then not retract it afterwards because
> of some pushback?
> 
I wasn't aware that we had made a decision.  I thought we were in discussion-mode.
In the meantime, dfaure's proposal (snippet below) looks good.  I think this is basically
what many of us have suggested but for some reason the simplicity got lost in the noise.
Should we also commit a tags/kdesupport-for-4.1/CMakeLists.txt file so folks can
easily build all of the kdesupport-for-4.1 stuff in 1 easy step?

dfaure writes:
Here's what I have in mind:
tags/kdesupport-for-4.1/
tags/kdesupport-for-4.1/phonon/    (svn cp'ed from tags/phonon/4.2.0)
tags/kdesupport-for-4.1/strigi/    (svn cp'ed from tags/strigi/strigi/0.5.11)
tags/kdesupport-for-4.1/qca/    (svn cp'ed from tags/qca/2.0.1)
etc.
Yes, just for convenience. Because nobody can remember 10 version numbers
that keep changing, for things he's not working on :-)