<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: arial;color: #000000">
I wish what you say were true, but Time Machine eventually can get to a point where it requires you to delete everything or start a new backup volume. This can happen when its size is considerably larger than the size of the drive it's backing up. I know this because it has happened to me. When it reaches that point it doesn't allow you to make ANY other changes, including deleting directories in the backup that you could do without. I exclude /opt/local from backups, along with other folders that can be readily reconstructed so that I won't run into this problem again.<div><br></div><div>Regards,</div><div><br></div><div>Geoff Odhner<br><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">On 4/26/2016 9:30:57 AM, Bachsau <web@bachsau.name> wrote:</p>René J.V. Bertin wrote on 26.04.2016 13:19:
<br>> Superfluous backing up of course ends up wasting significant amount of space on the backup disk esp. for developers who regularly to something like `port -n upgrade --force` after an incremental rebuild with only minimal changes. It is also costly in terms of time when you're using a NAS like my Time Capsule (even when connected via a wired gigabit connection).
<br>
<br>In default configuration time machine will automatically discard old
<br>backups in favor of new ones, so there shouldn't be any space problems
<br>ever.
<br>
<br>_______________________________________________
<br>macports-users mailing list
<br>macports-users@lists.macosforge.org
<br>https://lists.macosforge.org/mailman/listinfo/macports-users
<br>
</blockquote></div></div>