Fwd: [MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.

Lawrence Velázquez larryv at macports.org
Thu Jun 25 10:07:56 PDT 2015


Forwarding message that didn't make it to the list.

vq

> Begin forwarded message:
> 
> From: "Eric A. Borisch" <eborisch at gmail.com>
> Subject: Re: [MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.
> Date: June 25, 2015 at 12:40:12 AM EDT
> To: Lawrence Velázquez <larryv at macports.org>
> Cc: Ryan Schmidt <ryandesign at macports.org>, "macports-users at lists.macosforge.org" <macports-users at lists.macosforge.org>
> 
> 
> 
> On Wednesday, June 24, 2015, Lawrence Velázquez <larryv at macports.org <mailto:larryv at macports.org>> wrote:
> On Jun 24, 2015, at 8:02 PM, Ryan Schmidt <ryandesign at macports.org <>> 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.
> >
> > A daemon to detect such actions is an interesting suggestion. This
> > could adversely affect performance. I'm also not sure how we would
> > instruct the daemon what changes are ok and what changes aren't. For
> > example, installing /opt/local/lib/libsomething.dylib without using
> > MacPorts would not be ok, but creating /opt/local/etc/something.conf
> > would probably be fine. Installing /opt/local/bin/something would be
> > bad, but a database server installed with MacPorts that modifies the
> > contents of /opt/local/var/db/something/ while it runs would be ok.
> 
> What functionality would this enable? We don't maintain a permanent
> local history of archives or the registry. We don't maintain old
> versions of the ports tarballs. We keep old binary archives on
> packages.macports.org <http://packages.macports.org/>, but that wouldn't help users who don't install
> from binaries. I don't think we can implement snapshot functionality
> without abusing the word "snapshot". Frankly, anyone who wants the
> ability to roll their installation back to a previous state should start
> making incremental backups.
> 
> <snark> If only on OS vendor would make an easy automated backup solution. </snark>
> 
> I can see the utility a "port verify active" or something similar that would check installed files against what's in the archives, but beyond that, this is out of scope, IMHO. A tar --compare, perhaps? This would be slow, but minimal to implement. I can't recall if checksums are kept in the archives off the top of my head, but that could be another route.
> 
>   - Eric

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20150625/fd410490/attachment.html>


More information about the macports-users mailing list