4 May
2011
4 May
'11
4:19 p.m.
On Wed, May 4, 2011 at 10:14 AM, Tom Gundersen <teg@jklm.no> wrote:
On Wed, May 4, 2011 at 3:53 PM, Dave Reisner <d@falconindy.com> wrote:
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
My initial thought would be to name it "service", since that is the equivilent command in redhat/debian distros, the only problem is that the service command behaves differently in these distros so it might cause cross distro confusion.