job000344
Closed
P4Connect does not respect the the typemap setup on the server.
This appears to have been reported in Job 175, but that job has been closed and the issue still remains.
If I have my server typemap set to make all .prefabs +l and all .cs files +w, whenver I add a new prefab or C# source file from within Unity it should automatically appear added to the default changelist with those filetype attributes, but they do not.
An example typemap set on the server:
# Perforce File Type Mapping Specifications.
#
# TypeMap: a list of filetype mappings; one per line.
# Each line has two elements:
#
# Filetype: The filetype to use on 'p4 add'.
#
# Path: File pattern which will use this filetype.
#
# See 'p4 help typemap' for more information.
TypeMap:
text+w //....cs
text+l //....prefab
Version Info:
Server version: P4D/DARWIN90X86_64/2015.1/1073410 (2015/06/11)
Server Operating System: Mac OSX 10.10.5
Unity Version: 5.1.3f1
P4Connect: 2015.2.122.0542
Client Operating System: Mac OSX 10.10.5
This appears to have been reported in Job 175, but that job has been closed and the issue still remains.
If I have my server typemap set to make all .prefabs +l and all .cs files +w, whenver I add a new prefab or C# source file from within Unity it should automatically appear added to the default changelist with those filetype attributes, but they do not.
An example typemap set on the server:
# Perforce File Type Mapping Specifications.
#
# TypeMap: a list of filetype mappings; one per line.
# Each line has two elements:
#
# Filetype: The filetype to use on 'p4 add'.
#
# Path: File pattern which will use this filetype.
#
# See 'p4 help typemap' for more information.
TypeMap:
text+w //....cs
text+l //....prefab
Version Info:
Server version: P4D/DARWIN90X86_64/2015.1/1073410 (2015/06/11)
Server Operating System: Mac OSX 10.10.5
Unity Version: 5.1.3f1
P4Connect: 2015.2.122.0542
Client Operating System: Mac OSX 10.10.5
- Status
- Closed
- Project
- perforce-software-p4connect
- Severity
- A
- Reported By
- colinbday
- Reported Date
- 10 years ago
- Modified By
- Norman Morse
- Modified Date
- 9 years ago
- Owned By
- colinbday
- Dev Notes
- Priority: High
To fix, I need to add a "disable internal typemap" flag and to check that the add path is still working correctly. - Type
- Bug
The change which closed Job 175 was specifically about the ".bytes" type which was defaulting (incorrectly) to text. It is now set to binary.
To satisfy this job, An option needs to be added to the configuration interface which disables all the default
type mapping which is hard-wired into P4Connect and instead lets the server select the data type from the Perforce typemap and standard rules.