4 May
2011
4 May
'11
4:14 p.m.
On Wed, May 4, 2011 at 3:53 PM, Dave Reisner
It's not a file conflict, but a PATH conflict. Calling 'rc' or using a '#!/usr/bin/env rc' shebang is likely the culprit. From community/plan9port's profile.d script:
Is there a convenient way to detect path conflicts (also in packages I have not installed)? I guess we will rename the rc script for the next release, but the question is to what? Any opinions? -t