Below: five brief questions, answers to which may be simple, plus some side notes.
================================ 1) binary_backup.tgz ================================ Q1: What's comprised within Chandler's binary_backup.tgz file? For me, this compressed archive is currently around 2.4% of the size of my repository. I don't intend to weed or move the (Mac OS X) default ~/Library/Application Support/Open Source Applications Foundation/Chandler/foo.default/binary_backup.tgz I note <http://markmail.org/message/dyn24te6ewxrhxkv>, <http://markmail.org/message/xdkq4j7kv6d7y3us>, and <http://markmail.org/message/a7z6gbb2eh5hs5mg> reference to revision 16483. <http://svn.osafoundation.org/viewvc/chandler?revision=16483&view=revision> is unavailable, I assume that reorganisation occurred. ================================ 2) backup.chex ================================ Q2: What's comprised within a Chandler .chex file? For me, this file is currently 80 KB. I don't intend to weed or move the (Mac OS X) default ~/Library/Application Support/Open Source Applications Foundation/Chandler/foo.default/backup.chex I note <http://markmail.org/message/rbr523jb2legmwb2>, and (outdated) http://chandlerproject.org/releasenotes>: > Automate Upgrade Process: User now have the option to let Chandler export > a .chex on quit. This is convenient for new users (small data base) with > fast machines. For old timers with thousands of items, there's an option > to bypass this (don't forget to export though before upgrading to a new > version of Chandler): > https://bugzilla.osafoundation.org/show_bug.cgi?id=11139 Bug #11139 > Automate upgrade process > ================================ 3) date/time-stamped .chex files ================================ If I'm satisfied with the integrity and value of the default backup.chex then: Q3: is it OK for me to remove other .chex files? I assume that Chandler keeps no internal reference to such files after their creation by the user. ================================ 4) __repository__.0* directories ================================ I don't intend to weed or move the (Mac OS X) default ~/Library/Application Support/Open Source Applications Foundation/Chandler/ps5LCCHy.default/__repository__ If I'm satisfied with the integrity and value of the default __repository__ then: Q4: is it OK for me to remove other __repository__.0* directories? I assume that Chandler keeps no internal reference to such directories after their creation by the user. ================================ Locations ================================ Q5: on Mac OS X, is ~/Library/Application Support/Open Source Applications Foundation/Chandler a reasonable location for user-created .chex files and __repository__.* backup directories? Beyond Chandler: standard backup routines apply, I don't rely on having these files/directories on my local hard disk alone. I backup to remote or external storage. --- Thanks for any advice Graham -- View this message in context: http://n2.nabble.com/Understanding-and-housekeeping-weeding-%281%29-binary_backup.tgz-%282%29-backup.chex-%283%29-date-time-stamped-.chex-files-%284%29-__repository__.*-directories-tp2109816p2109816.html Sent from the Chandler users mailing list archive at Nabble.com. _______________________________________________ [email protected] mailing list unsubscribe here: http://lists.osafoundation.org/mailman/listinfo/chandler-users Chandler wiki: http://chandlerproject.org/wikihome
