[p4] Mac OS X and long filenames
Nick Pisarro
nickp at aperture.com
Thu Jan 24 19:12:58 PST 2002
I have been running with a version of P4 that works fine with long
filenames and MacOS X for quite some time. So, it probably is not an
operating system issue.
But the version of p4 I installed, I believe, was a PPC Unix/linux
version, rather than a one Labeled Mac OS X. I have been running it from
the tcsh shell using the "Terminal" program. It has been installed so
long, I can't say exactly what I installed.
Nick Pisarro
kmac at apple.com writes:
>I find this posted a while back, but I find no answer on
>the list.
>
>One of my users just ran into this same problem.
>
>Has anyone heard anything from perforce about this? Is it actually
>a perforce bug? Or is it some issue with OS X or with
>the partition type or...
>
>Thanks-
>
>
>-Karl (kmac at apple.com)
>
>
>----- Forwarded message from Jon Witort <jon at witort.com> -----
>
>> From: "Jon Witort" <jon at witort.com>
>> To: <perforce-user at perforce.com>
>> Date: Tue, 9 Oct 2001 12:55:42 -0700
>> X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
>> Subject: [p4] Mac OS X client doesn't appear to support long
>filenames...?
>>
>> Despite the reassurance that the Mac OS X p4 client supports filenames
>> longer than 31 characters:
>>
>> http://www.perforce.com/perforce/technotes/note019.html
>>
>> ... I find that this is not the case. I've tried it both on UFS and HFS+
>> volumes, and in both cases p4 fails to sync files with >31 character
>> filenames to my client. My workaround has been to:
>>
>> p4 print -q reallyreallyreallylongfilename.c >
>reallyreallyreallylongfilename.c
>> p4 sync reallyreallyreallylongfilename.c
>>
>> No, I'm not accidentally running the classic Mac OS version of p4; the
>Mac
>> running UFS didn't even have classic installed.
>>
>> cheers,
>> jon
More information about the perforce-user
mailing list