On Oct 9, 2014, at 1:18 AM, steve jenkin <stevej098l...@gmail.com> wrote:
> I’m worried about the "/opt/local/bin/port” series of executables. > If they change, I won’t get the upgrades, forcing me to reinstall macports > from scratch. But now at least I have a port/package list if that happens. > > I tried port “Macports” for those executables, but the port is very definite > that ordinary mortals shouldn’t install it - it puts files outside the > /opt/local tree - so I didn’t install it. Not sure what you're worried about? Those executables are part of MacPorts base. If you reinstall MacPorts to /opt/local (which happens during "port selfupdate" if a base update is available), they'll be overwritten. This is entirely fine. > /opt/local/bin/llvm-ld-mp-3.1 > /opt/local/bin/llvm-stub-mp-3.1 These look like they're from llvm-3.1. > /opt/local/bin/daemondo > > /opt/local/bin/port > /opt/local/bin/port-tclsh > /opt/local/bin/portf > /opt/local/bin/portindex > /opt/local/bin/portmirror These are part of MacPorts base. > /opt/local/bin/ppl-config > /opt/local/bin/ppl_lcdd > /opt/local/bin/ppl_lpsol > /opt/local/bin/ppl_pips These are from ppl. vq _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
