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:Karl Elvis MacRae (km@apple.com)
Date:01/25/2002 10:50:38 AM
List:com.perforce.perforce-user

On Fri, Jan 25, 2002 at 10:43:37AM -0800, Michael Bishop spake thus:

At 10:12 PM -0500 1/24/02, Nick Pisarro wrote:

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.

There are two command-line clients that run on Mac OS X.

There's the confusion. This is not clear on your web site. What's even worse is that there are different answers to this in different places, and the download page lists the OSX client under "mac" and teh Darwin client under "unix", which is pretty lame.

The other is for Mac OS X and in fact, will not run under Darwin because it is linked to Carbon. It used to use the c standard APIs to do everything but resource forks. That changed in 2001.1 to use FSSpecs for everything (whoops, that brought back in the 31 char limitation) and now (2002.2 uses FSRefs for nearly everything so we're back in business. The reason it uses Carbon calls at all is so it can access the resource forks of files.

The question is, when can we get hands on the 2002.2 release for OSX?

-Karl