renaming MacPorts' install directory - how to handle the TM backup(s)?

Jeremy Lavergne jeremy at
Mon Sep 8 08:58:50 PDT 2014

You made sure it counted unique inode filesize and not recount them each time?

On September 7, 2014 2:10:12 PM EDT, "René J.V. Bertin" <rjvbertin at> wrote:
>On Sunday September 07 2014 13:16:50 Brandon Allbery wrote:
>> Yes, I was saying any operation other than actually writing the file
>> be safe, and then saying what would be needed in the
>> actually-writing-the-file case to make it safe.
>/Volumes/Time Machine Backups/Backups.backupdb/portia
>36808955 0 drwxrwxr-x+ 19 bertin admin 782 Sep  2 18:57
>36982951 0 drwxrwxr-x+ 19 bertin admin 782 Sep  7 19:12
>36982951 0 drwxrwxr-x+ 19 bertin admin 782 Sep  7 19:12
>and 9.6Gb was copied. The 2 (sic) directories above are each 9.8Gb
>tall, so it would seem that despite my efforts to make the most recent
>backup reflect the changes I made since then, the full MacPorts tree
>was copied. Meh.
>It also seems that more than half the space MacPorts takes on my work
>disk is taken up by files I've excluded from being backed up ...
>macports-users mailing list
>macports-users at

More information about the macports-users mailing list