On Wo, 2008-10-01 at 08:14 -0700, Wil Clouser wrote: > Ah, thanks Wynand. > > I don't think a longer error message is the answer unless it only > appears at startup; otherwise it just fills up logs. > > Since the functionality is still there despite the error message I > think the check should be moved to an "install requirements" part of > the test suite or a status monitor page. > > Wil
The message is more of a catchall if the indexers couldn't be initialised. Apart from missing libraries, something like a corrupt index could also cause the indexing to not initialise, and then it warns for that project/language combination that indexing will be enabled. I thought this will be useful for admins to see why searching is slow (which is will be in big projects if the indexer couldn't be initialised). So you will keep on seeing them in the log for each project/language on first access... Reasonable for now? Keep well Friedel ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
