Changes by: Nathaniel Gray (n8gray at caltech.edu)
Date: 2007-05-01 15:48:44 -0700 (Tue, 01 May 2007)
Revision: 103
Log message:

      Added a limitations section to the readme.  Updated some comments.  Removed the
     sleep from the creation date test.

Changes by: Nathaniel Gray (n8gray at caltech.edu)
Date: 2007-05-01 17:12:24 -0700 (Tue, 01 May 2007)
Revision: 104
Log message:

      Waah!  The ACL tests were totally borken, but they're fixed now.
     
     The creation-date test was also a bit problematic.
     
     Removed ACL test for symlinks -- they don't have 'em.

Changes by: Nathaniel Gray (n8gray at cs.caltech.edu)
Date: 2007-05-01 18:03:44 -0700 (Tue, 01 May 2007)
Revision: 105
Log message:

      Testing the release-tag target.

Changes by: Nathaniel Gray (n8gray at cs.caltech.edu)
Date: 2007-05-01 18:13:25 -0700 (Tue, 01 May 2007)
Revision: 106
Log message:

      Added release targets to the makefile.  Now I'll try packaging the 0.1.1
     release.

Changes by: Nathaniel Gray (n8gray at cs.caltech.edu)
Date: 2007-05-01 18:13:42 -0700 (Tue, 01 May 2007)
Revision: 107
Log message:

      Release 0.1.1

Changes by: Nathaniel Gray (n8gray at cs.caltech.edu)
Date: 2007-05-01 18:20:56 -0700 (Tue, 01 May 2007)
Revision: 108
Log message:

      set post-release version.
     Added upload target to makefile.

Changes by: Nathaniel Gray (n8gray at cs.caltech.edu)
Date: 2007-05-06 12:21:18 -0700 (Sun, 06 May 2007)
Revision: 109
Log message:

      Added ctool, a tool to checksum binaries while ignoring their prebinding
     headers.

Changes by: Nathaniel Gray (n8gray at cs.caltech.edu)
Date: 2007-05-07 16:03:50 -0700 (Mon, 07 May 2007)
Revision: 110
Log message:

      Use sudo when clearing bsd flags, just in case.
     
     Clean up the hardlinks test tempfile.
     
     Xar needs the -P flag to preserve permissions.
     
     Fixes to ctool to prevent compiler warnings.
     
     'make' will make ctool now too.  
     
     TODO: Integrate ctool into the copier meta info.

Changes by: Nathaniel Gray (n8gray at cs.caltech.edu)
Date: 2007-05-07 18:28:12 -0700 (Mon, 07 May 2007)
Revision: 111
Log message:

      Added a test for aliases.  The methodology here is debatable.  I believe that if
     you're backing up /foo and hit an alias to some file /foo/bar, when you restore
     (or copy) to /baz the alias should point to /baz/bar.  If the alias points to
     /random/boing (outside the tree you're backing up) then it should stay pointing
     there.  However, I suspect somebody could convince me that this is a bad idea.
     
     This is complicated because:
         * Aliases are finder things, not filesystem things
         * Carbon "Alias" interfaces are *not* for the finder things, they're for
             an in-memory representation of a file that *acts* like the finder thing
         * You can have absolute or relative in-memory aliases
         * I don't know what the finder creates, but I think they're absolute.