Moving ThreadWeaver to kdelibs

[Mirko Boehm]

On Tuesday 13 September 2005 10:50, Zack Rusin wrote:
> > I suggest you put it as subdir to kdelibs and have kdecore link it
> > in. We will do the sorting later. And please: stick to the naming
> > within kdelibs - no capital letters. Or let someone else do the job
>
> I think we talked about this during the conference: no (I'll repeat
> because the "no" is crucial) _no_ class will be moved to kdecore as a
> component without a staging area in a static library. If something will
> prove useful and will actually start getting used (plus will get some
> testing) then we move it to kdecore. We need to create a static
> libkdehelpers/libkdeextras/libkdebeta or something like that to stage
> those component and we might as well do it right now since this is the
> exact scenerio where we would like to use it.
I am fine with that. Initially, I wanted to wait for some usage experience 
from other parts anyway. Also, some API changes can be expected along with 
this. 

So where is the static library stage area? 

--Mirko.
-- 
KDE e.V.: http://www.kde.org/areas/kde-ev/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050913/90f3843b/attachment.sig>