Moving the proxy model test suite to kdesupport?

Stephen Kelly steveire at
Thu Jul 15 14:28:14 BST 2010


I'd really like to get this resolved and finished so I'll try again to find 
what the problem is.

I'm not certain it was clear before that this is not a dependency for any 
shipped application. The only useful reason to install this is for local 
debugging in a simple way. 

Tom Albers wrote:
> On Wed, 07 Jul 2010 00:41:27 +0300, Ingo Klöcker <kloecker at> wrote:
>> If you don't want to guarantee BC then it does not belong into
>> kdesupport IMO. kdesupport contains dependencies for kdelibs and all of
>> those really should keep BC.
> Indeed, definitely not kdesupport.
>> If you do not want to guarantee BC then
>> keep it in a private location, do not install it anywhere and have
>> everybody who wants to use it copy it. You could move it to kdesdk
>> (without installing it).
> Or extragear or playground.
Neither extragear nor playground would work as kdeui/tests/proxymodeltestapp 
depends on it. So it needs to be in kdelibs or a dependency of kdelibs.

/trunk/tests wouldn't work for the same reason.

So in the interest of moving this along, this is what I want to do:

install the proxymodeltestsuite library if it is built (it is only built if 
KDE4_BUILD_TESTS is true).
install the headers to ${INSTALL_LOCATION}/private
not keep BC in the library.
not make the library part of ${KDE4_KDEUI_LIBRARIES}
not have the library packaged
not have any applications link to it or use it

If an application developer wants to debug an application (like kmail) they 
can locally add a link to the library and that's it. No application will 
ever ship which links to it, so I don't see any reason to version it or 
maintain .so numbers.

Is there any reason I'm not aware of that the above would not work?

All the best,


More information about the kde-core-devel mailing list