On Wed, Jun 24, 2015 at 11:03 PM, Lawrence Velázquez <[email protected]> wrote:
> On Jun 24, 2015, at 8:02 PM, Ryan Schmidt <[email protected]> wrote: > > > On Jun 24, 2015, at 5:10 PM, Christopher Ramos wrote: > > > >> Perhaps it would be feasible to employ an agent or daemon that logs > >> all changes to a user's installation. That way, if it's ever bungled > >> by an "outside force," the user could do something like "sudo port > >> revert snapshot-06222015". This would remove any files not > >> registered by the daemon to have been present at the time of the > >> requested snapshot; if need be, previously installed or files (or > >> files that were in a different state) would retrieved from the > >> Internet. > Simple way to check for changes: 1) install gnutar 2) uninstall inactive 3) run this shell script: #!/bin/sh for x in /opt/local/var/macports/software/*/*.tbz2; do echo "Checking `basename $x`" gnutar --warning=no-unknown-keyword --exclude='./+*' -C / --compare -jf "$x" done You can run under sudo to check files set with access restrictions (config scripts for some servers.) Not the fastest -- doesn't leverage checksums already in .tbz file (+CONTENTS) -- but it works. - Eric
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
