On Sat Aug 11 2012 Sriram Karra wrote: > I have rewritten along lines you have suggested and pushed it. Please take a > look.
Looks fine to me, thanks, > Backwards compatibility for me would mean a few distinct things: > > 1. Will my old customizations work with the new code > #1 might never get fixed given the direction we've headed. My intention has been to make the concepts more transparent. So yes, making old customizations work in an automated would be very difficult. > 2. If I use BBDB v3 and don't like it can I go back to v2 > #2 can and should get fixed. I find it quite amusing in fact, the > bbdb-migrate stuff has always had the hooks to downgrade to an > earlier file format version - until now, i.e., when it is needed > more than ever before really :) One of these days... Well, the new format allows you to do things you could not do with the old format. So going back to v2 is only possible by throwing away the incompatible extensions in the format of v3. I do not consider this a satisfactory procedure. Of course, anyone switching from v2 to v3 should first make a copy of his or her old database. Then if things do not work out for whatever reason you can fully go back. Roland ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
