On Jun 26, 2014, at 4:33 PM, René J.V. Bertin wrote:
> On Jun 26, 2014, at 23:17, Ryan Schmidt wrote:
>
>>> NB: if like me you get registry errors ("file name too long") since having
>>> upgraded to MacPorts 2.3.0, you'll have noticed as I that those sort
>>> themselves out, possibly requiring you to repeat certain commands.
>>
>> This is the first I've heard of this problem. Have you filed a bug report?
>> Are your paths (prefix, or path to the ports tree) unusually long?
>
> Hmmm. No, I haven't filed a report because the issue corrects itself, and I
> thus cannot even reproduce it myself for a given port.
> I don't think my paths are unusually long, /opt/local is a symlink pointing
> to /Volumes/Debian/MacPorts ...
And is your configured MacPorts prefix /opt/local or /Volumes/Debian/MacPorts?
Because we previously had a bug when your configured prefix is a symlink to
somewhere else, which was supposed to have been solved, but maybe there is a
second problem still with that configuration.
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
