Setting up a new Helix Core Depot

1. To stop a running server use p4 admin stop 

2. Refer to the Helix Core Server Administrator Guide for information on starting the server

3. edit typemap

    p4 typemap

The simplest configuration is to require exclusive locking on all files:

Typemap:
   +l //...

4. Create the directory where you will add data to Perforce

      mkdir /tmp/my_import_dir
      cd /tmp/my_import_dir

4. Create a new client to populate the depot

       p4 client import_client

           By default the Root directory is the current working directory.
           Define the View to map the data on disk to the desired depot structure, for example

       View:
            //depot/<library>/<ip>/trunk/...  //import_client/...

       See the repo_path field discussion on the Creating New IPs page, which shows the recommended depot structure for use with IPLM - you can use a similar structure even if not using IPLM

        5. Copy the Cadence libraries into the desired location under the import directory, e.g.

        mkdir cds
        cp -r <location_of_existing_cadence_library> cds

6. Add 'DMTYPE versic' to the cdsinfo.tag of libraries to be imported

Sample cdsinfo.tag contents:

      CDSLIBRARY
      NAMESPACE LibraryUnix
      DMTYPE versic

7. Create a .p4ignore file to exclude unwanted files (see Ignoring Files with P4IGNORE)

8. Create a .p4config file containing the following

      P4CLIENT=import_client
      P4IGNORE=.p4ignore
      P4PORT=1666

9. set the P4CONFIG environment variable to point to the config file you just created

    export P4CONFIG=.p4config

10. Add the files to the depot

p4 add cds/...

(verify that no unwanted files were added in this step - you can run p4 opened ...to view the list of files that were added.
 p4 revert any unwanted files then update the P4IGNORE file to prevent them being added later)

11. Submit (checkin) the files

p4 submit -d '<my commit message>'