moving strigi

Christian Ehrlicher Ch.Ehrlicher at gmx.de
Wed Feb 28 18:26:31 GMT 2007


Jos van den Oever schrieb:
> 2007/2/28, Christian Ehrlicher <Ch.Ehrlicher at gmx.de>:
>> Jos van den Oever schrieb:
>> > 2007/2/28, Dirk Mueller <mueller at kde.org>:
>> >> On Tuesday, 27. February 2007, Jos van den Oever wrote:
>> >>
>> >> > If all goes well, I'll finish the kfilemetainfo for kdelibs and
>> >> > kdebase for next monday. In preparation of that I'd like to move
>> >> > strigi to a more visible place in svn: trunk/kdesupport/strigi
>> >>
>> >> Does that mean that kdelibs and kdebase will require strigi to be
>> >> installed?
>> >> If so, the building documentation should be updated.
>> > Yes it will. So far no index is required, so CLucene or sqlite are not
>> > required yet. Only the metadata and text extraction functionality will
>> > go in for now. This means the only required dependencies are
>> > libcrypto, libz and libbz2. libmagic and libexpat/libxerces are
>> > optional.
>> >
>> So why not moving strigi directly into kdelibs instead adding a new
>> depedency?
> 
> This may sound strange, but Strigi is useful without KDE. I will
> continue releasing it as an independent library. It contains libraries
> and programs that are quite useful for other desktop search tools and
> programs that need to have a nice api for getting at metadata or
> embedded files.
> Check my FOSDEM presentation for the details:
> http://www.kde.org/kdeslides/fosdem2007/2007-02-vandenoever-strigi_internals.pdf 
> 
Sorry, I did not notice that you put it into kdesupport.
So it's a 'third-party' lib like kdewin32 :)

Christian





More information about the kde-core-devel mailing list