<div dir="ltr">On Wed, Jun 24, 2015 at 11:03 PM, Lawrence Velázquez <span dir="ltr"><<a href="mailto:larryv@macports.org" target="_blank">larryv@macports.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On Jun 24, 2015, at 8:02 PM, Ryan Schmidt <<a href="mailto:ryandesign@macports.org">ryandesign@macports.org</a>> wrote:<br>
<br>
> On Jun 24, 2015, at 5:10 PM, Christopher Ramos wrote:<br>
><br>
>> Perhaps it would be feasible to employ an agent or daemon that logs<br>
>> all changes to a user's installation. That way, if it's ever bungled<br>
>> by an "outside force," the user could do something like "sudo port<br>
>> revert snapshot-06222015". This would remove any files not<br>
>> registered by the daemon to have been present at the time of the<br>
>> requested snapshot; if need be, previously installed or files (or<br>
>> files that were in a different state) would retrieved from the<br>
>> Internet.<br></blockquote><div><br></div><div>Simple way to check for changes:</div><div>1) install gnutar</div><div>2) uninstall inactive</div><div>3) run this shell script:</div><div><br></div><div>#!/bin/sh</div><div>for x in /opt/local/var/macports/software/*/*.tbz2; do</div><div> echo "Checking `basename $x`"</div><div> gnutar --warning=no-unknown-keyword --exclude='./+*' -C / --compare -jf "$x"</div><div>done</div><div><br></div><div>You can run under sudo to check files set with access restrictions (config scripts for some servers.)</div><div><br></div><div>Not the fastest -- doesn't leverage checksums already in .tbz file (+CONTENTS) -- but it works.</div><div><br></div><div> - Eric</div></div></div></div>