This branch makes some drastic changes to how mbox and maildir sources work. There's no longer any state associated with a source between Sup runs - no cur_offset or mtimes in sources.yaml. Instead, the source queries the index to find out which messages it's already seen and which messages are new. This enables a much more robust maildir implementation that detects the addition or deletion of any message.
It's not totally done yet. It'll detect that a maildir message has been deleted, but it doesn't yet remove the old location from the index so renames are unlikely to work. There needs to be UI code to handle the case where a message matches a search but has been deleted from all sources, and probably a utility to remove such messages from the index. I expect sup-sync-back to be broken. Keeping track of multiple locations per message requires an index format change. The upgrade process is trivial and done automatically but you won't be able to use that index with an older Sup. For now if you want to try this out I suggest using a different SUP_BASE. I'd appreciate any comments about the code or general approach. If anyone would like to contribute an email corpus for the unwritten testsuite or pseudocode out some testcases that would be very helpful too. _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel
