Excerpts from Ethan Glasser-Camp's message of Fri Mar 27 18:22:06 +0100 2009: > Hi, long time reader, first time caller. > > Many years ago I used fetchmail+Mutt to handle my mail, but all my > configuration was lost in a hard drive crash and I didn't have the > energy to recreate it. So as I look at sup, I am judging how difficult > it is to keep its configuration in a git repo (for easier replication > and backup). > > One problem I see is that sources.yaml contains both all the information > about how to access a source, and its current state. I would like to > keep the first in version control, and the second not. So I would like > sources.yaml split into a sources.yaml and a sources-state.yaml; the > first one would be the information about how to access the sources, and > the second one would map source ID to its cur_offset.
I keep my sup configuration including the whole sources.yaml file in a darcs repository. Even if the data was split in two files I would prefer to also save it. About backups, I recommend sup users to make regular sup-dump's, not only because sup still have bugs but also because it's the only (meta)data needed to reconstruct your index. **NOTE to sup developers** Moreover I think that sup should write a log file being some kind of sup-dump delta: messageid (oldlabel1 oldlabel2 -> oldlabel2 newlabel3) ... I think I will try to implement this feature soon. -- Nicolas Pouillard _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
