Exception for Dolphin - KFileMetadataWidget

Vishesh Handa me at vhanda.in
Fri Dec 21 13:21:45 UTC 2012


On Fri, Dec 21, 2012 at 6:32 PM, Sebastian Kügler <sebas at kde.org> wrote:

> On Friday, December 21, 2012 16:27:17 Vishesh Handa wrote:
> > So, may I merge my patch into kde-baseapps 4.10? It will get tested more
> > thoroughly in RC2.
>
> I'm very uneasy with merging something this big and intrusive into 4.10 at
> this point. I also don't see why it has to go into 4.10, sure, it's all
> nice,
> but certainly not critical, especially since ...
>

It means shipping un-maintained code which is slow and has documented bugs.
I personally think it is better to ship actively maintained code where
there is a developer to fix any bugs (if they should be), than something
old and stale.


> Would it not cause functional regressions, since the old indexer would
> index
> many more file types than the new indexing services in nepomuk-core?
>

Just so that everyone is clear. We are talking about the case when Nepomuk
is disabled / the file has not metadata in Nepomuk. In that case,
KFileMetadataInfo used to temporarily index the file via strgi, and display
the results. The Nepomuk2::FileMetadata widget does the same, but it uses
the nepomuk indexer, and not strigi.

This has nothing to do with the actual file indexing.

Regarding functional regressions - Not really. The only big difference is
office based formats, which my indexer still doesn't target. I'm still
working on that, I should have it ready by RC2. We also handle pdfs which
strigi does not.

Also, considering that amount of testing Nepomuk is going through cause of
the new indexer, I'm fairly certain we will have greater coverage than
Strigi. There is also the issue of stability and speed.


--
> sebas
>
> http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
>



-- 
Vishesh Handa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20121221/206496c3/attachment.html>


More information about the release-team mailing list