Fisheye can communicate with any Perforce server, but it needs to use the P4 command-line client to do so. By default, Fisheye looks for the P4 executable in the current path. However, if necessary you can set the exact path to the P4 client executable in Fisheye, as described on this page, before you to Fisheye. Please see the page for information about the versions of Perforce that are supported by Fisheye. Configuration To set the location of the Perforce client: • Go to the in Fisheye.

Perforce Helix MacOS client programs determine Perforce file type as follows: MacOS client programs check the first 1024 bytes of the file's data fork and apply the following logic: If the first 1024 bytes contain only text, the text file type is assigned. Fisheye can communicate with any Perforce server, but it needs to use the P4 command-line client to do so. By default, Fisheye looks for the P4 executable in the current path.

• Click Server (under 'Global Settings'). • Click Edit Details (under 'Perforce client'). • Enter the path to your P4 (Perforce) binary executable. • Click Update.

• Restart your Fisheye server. Files incorrectly considered binary Some users have reported errors where Fisheye considers some files to be binary when they are not. It appears this may be a limitation of earlier P4 clients. Download .net framework for mac. If you can upgrade to a recent P4 client (2006.1 onwards), this will fix this issue. You do not need to update the P4 Server. Please note that the repository will need to be reindexed in Fisheye after upgrading the P4 client for the changes to be picked up.

If you are unable to upgrade to a recent P4 client, the page in Fisheye allows you to set a limit on the size of filelog commands sent to the server. Setting this to something around 100 will fix the issue.

It will, however, also impact performance significantly.

The Adobe Source Libraries have migrated away from the SourceForge CVS/Subversion servers in favor of a Perforce server that is hosted on stlab.adobe.com. Guest access for this server is enabled, allowing anonymous users to grab snapshots of the current release sources as well as the current working set of sources for the upcoming release.

The primary difference between Perforce and other CMS services like CVS or Subversion is that the state of the client’s image of the depot (repository in CVS parlance) is stored server-side, not derived client-side. This requires the creation and maintenance of per-user clientspecs (client path mapping specifications), and branchspecs (file/directory branching specifications). The following steps will guide you through two mutually-exclusive scenarios. In either case you will have to download the Perforce client first. Contents • • • • Perforce Depot Location The Adobe Source Libraries’ Perforce depot is at. Stlab.adobe.com:10666 Downloading Perforce The Perforce client software is free and can be downloaded for,,,, and a host of. Each operating system at a minimum has a command-line binary available.

For some operating systems there are GUI front end applications available as well (, ). If you are following these instructions you will want to download the command-line client, and place the p4 application in a directory that is in your computer’s PATH. Scenario 1: Using p4checkout p4checkout is intended to emulate the CVS checkout command, grabbing a snapshot of the state of the ASL depot and copying it to your local computer. The pros of this method are that it is anonymous and very easy to execute. The cons of this method are that there is no permanent record-keeping, and as such you will not be able to submit any changes to the Adobe Source Libraries. This method is recommended for users of the Adobe Source Libraries who are interested in the state of the depot without having a desire to contribute directly to the project. If you are on Windows machine, download the following batch file If you are on Mac OS X, Linux, or some other *nix-compatible system, there is a bash shell script to download: When you have this file downloaded (either version), you simply place it in the directory you would like to serve as the root directory for your local copy of the ASL depot, and you run it.