Some notes of mine on /usr/local: I can't avoid /usr/local entirely, since VirtualBox and Parallels install their command line tools there. But I can move /usr/local out of the way, for the duration of MacPorts builds, as necessary. More precisely, with System Integrity Protection turned off, I moved /usr/local elsewhere (not in /usr, which is mostly protected), and replaced it with a symlink to the new location. That way, I can rename what the symlink points to, without necessarily needing to leave SIP turned off. I also put certain items that need to always be available at the same path, in another subdirectory of the directory containing /usr/local; specifically, a PAM module, a recompile of linux pam_ssh_agent_auth, which once configured, allows su or sudo without password if one could e.g. ssh root@localhost with keys; the catch being if it's not in one of the usual locations (possibly including /usr/local/lib, I'm not sure), the module has to appear in the PAM configuration file using a full pathname.
> On Aug 4, 2017, at 20:16, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Aug 4, 2017, at 17:25, Jerry wrote: > >> I just ran port selfupdate after several months and experienced the >> following oddities. >> >> >> * readline was reported as disabled: >> >> $ sudo port selfupdate >> Password: >> ---> Updating MacPorts base sources using rsync >> MacPorts base version 2.4.0 installed, >> MacPorts base version 2.4.1 downloaded. >> ---> Updating the ports tree >> ---> MacPorts base is outdated, installing new version 2.4.1 >> Warning: Disabling readline support due to readline in /usr/local >> >> There is no readline directory in /usr/local. > > It didn't say "readline directory"; it said "readline", meaning the readline > libraries libreadline or libhistory were found in /usr/local/lib and/or the > readline headers were found in /usr/local/include/readline. This is not > supported. See: > > https://trac.macports.org/wiki/FAQ#usrlocal > >
signature.asc
Description: Message signed with OpenPGP
