6 messages in com.perforce.perforce-user[p4] Mac OS X and long filenames
FromSent OnAttachments
Karl Elvis MacRae24 Jan 2002 18:40 
Michael Bishop24 Jan 2002 18:55 
Nick Pisarro24 Jan 2002 19:12 
Mike Castle24 Jan 2002 19:33 
Michael Bishop25 Jan 2002 10:43 
Karl Elvis MacRae25 Jan 2002 10:50 
Subject:[p4] Mac OS X and long filenames
From:Michael Bishop (supp@perforce.com)
Date:01/24/2002 06:55:21 PM
List:com.perforce.perforce-user

At 6:41 PM -0800 1/24/02, Karl Elvis MacRae wrote:

I find this posted a while back, but I find no answer on the list

2001.1 introduced a bug that put the 31 char limit back in place.

2002.1 will fix that for both the Mac Classic clients and Mac OS X clients as it uses the FSRef APIs.

However, the directory scanning has not yet been updated so there is a limit on the length of directory names. Hopefully this won't be a problem, but if it is for your development, send something to support at perforce.com

_ michael

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

----- End forwarded message -----