RFC: Location for KexiDB and 3rdparty libs like sqlite

[Jaroslaw Staniek]

Andreas Pakulat said the following, On 2007-06-25 12:58:

> Huh? Maybe I'm wrong, but can't stuff in playground depend on any KDE
> module? Its not very likely a DB plugin for KDevelop would go into the
> kdevelop module. Rather it would live in playground/devtools and be
> available via <whatever we come up with for easy plugin installation>. 

KexiDB resides in trunk/koffice/kexi/. Why I have mentioned moving it is 
because plugins could cannot use it this way. Once KexiDB moves eg. to 
playground, it can be used without copying the source code tree or changing 
build system recipes.
Part of the goal would be to let packagers prepare their specs early enough.

> So having that in koffice/libs and having the plugins using it in
> playground shouldn't pose a problem, unless of course I'm mistaken.
> 
>> 	dfaure	it's exactly the same: used by all modules, so it must remain BC once 
>> 4.0 is out.
>> 	dfaure	we expect the same quality of kdesupport code, it's just that it's 
>> packaged separately.
>> 	jstaniek	so maybe my case re BC policies and packaging is simialr to kdevelop, 
>> so I can reside in KDE/{somenewdir} ?
>> 	dfaure	you think kdevplatform won't keep BC??
>> 	jstaniek	its BC is not KDElibs BC right?
> 
> In fact it will keep BC just as kdelibs (except for the plugins subdir).
> However it will only keep BC once it is released and this will not
> happen together with KDE 4.0.

Same with KexiDB; I mean: the timeline is different.

-- 
regards / pozdrawiam, Jaroslaw Staniek
  Sponsored by OpenOffice Polska (http://www.openoffice.com.pl/en) to work on
  Kexi & KOffice: http://www.kexi.pl/en, http://www.koffice.org
  KDE3 & KDE4 Libraries for MS Windows: http://kdelibs.com, http://www.kde.org