> On Aug 6, 2017, at 14:59, Ryan Schmidt wrote:
>
>
>> On Aug 4, 2017, at 20:36, Richard L. Hamilton wrote:
>>
>> Some notes of mine on /usr/local: I can't avoid /usr/local entirely, since
>> VirtualBox and Parallels install their command line tools there.
>
> Those probably won't cause pr
> On Aug 4, 2017, at 20:36, Richard L. Hamilton wrote:
>
> Some notes of mine on /usr/local: I can't avoid /usr/local entirely, since
> VirtualBox and Parallels install their command line tools there.
Those probably won't cause problems for MacPorts.
> But I can move /usr/local out of the wa
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,
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
On 08/05/2017 12:25 AM, list_em...@icloud.com wrote:
> * 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
>
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.
---> Upd
