| | 1 | = Perforce = |
| | 2 | |
| | 3 | [http://www.perforce.com/ Perforce] is a popular centralized commercial revision control system that's used in many corporate environments. It can only be used as a SourceRepository at this time using the prefix '''p4:''' |
| | 4 | |
| | 5 | == Usage == |
| | 6 | |
| | 7 | Below is an example config used during testing: |
| | 8 | |
| | 9 | {{{ |
| | 10 | [jam] |
| | 11 | root-directory = /tmp/jamstate/ |
| | 12 | source = p4:jam |
| | 13 | target = hg:jam |
| | 14 | state-file = jam.state |
| | 15 | |
| | 16 | [p4:jam] |
| | 17 | # Perforce "port" (in this case, the public server perforce maintains) |
| | 18 | p4-port=public.perforce.com:1666 |
| | 19 | # The name of your client |
| | 20 | p4-client=myhostname-tailortest |
| | 21 | # The path within the depot to track (used both to find changes as well as map files) |
| | 22 | depot-path = //public/jam/src/ |
| | 23 | # Place where the files will show up after a sync |
| | 24 | root-directory=/tmp/pubtest/jam/ |
| | 25 | |
| | 26 | [hg:jam] |
| | 27 | # Note: Using the same root-directory as above. |
| | 28 | root-directory=/tmp/pubtest/jam/ |
| | 29 | }}} |
| | 30 | |
| | 31 | The perforce client used above contains the following root and view: |
| | 32 | |
| | 33 | {{{ |
| | 34 | [...] |
| | 35 | |
| | 36 | Root: /tmp/pubtest/ |
| | 37 | |
| | 38 | View: |
| | 39 | //public/jam/src/... //myhostname-tailortest/jam/... |
| | 40 | |
| | 41 | [...] |
| | 42 | }}} |