[KinoSearch] KinoSearch::Search::SortRule seems not to allow type parameter

Marvin Humphrey marvin at rectangular.com
Sun May 3 16:48:49 PDT 2009


On Sat, May 02, 2009 at 06:18:21PM -0400, Darian Anthony Patrick wrote:
> In general do you want to hear about issues with trunk, or would you rather
> that we just hold off until a dev release is made?  I know some projects are
> annoyed with reports of problems with trunk.

I would prefer to hear.

KS doesn't have a "stable trunk" policy per se, in that you won't always be
able to "svn up" and have existing apps continue to work.  First, the file
format and API remain in flux.  Second, it's hard to keep memory leaks from
creeping in -- I don't run "./Build test_valgrind" before every commit because
it takes half an hour and won't run natively on the OS X laptop where I do
most development.

Nevertheless, I try to keep trunk in an internally consistent state -- so that
ideally, any particular repository revision should work in isolation.

In other words, it ought to be possible to check out svn trunk, verify that
"./Build test" and "./Build test_valgrind" both pass, troubleshoot your apps
until they stop crashing (nearly all API mods are implemented in such a way as
to cause catastophic failure rather than subtle misbehavior), regenerate your
indexes from scratch, and go.

Marvin Humphrey






More information about the kinosearch mailing list