# The form data below was edited by tom_tyler # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. Job: SDP-264 Status: suspended Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2017/10/25 21:28:12 ModifiedBy: tom_tyler ModifiedDate: 2017/10/25 21:39:57 OwnedBy: tom_tyler Description: CASE_SENSITIVE=1 setting in mkdirs.cfg is ignored in OSX. The UNIX SDP uses a symlink for 'p4d' if CASE_SENSITIVE=1, or else a tiny wrapper script if CASE_SENSITIVE=0 that passes in the '-C1' flag to p4d, along with other args. This produces the desired result on UNIX/Linux systems, which are inherently case-sensitive. When run on Mac, however, the symlink is used, which result in a case-insensitive server on Mac. While this may be preferable as that is the default, but it may be confusing the CASE_SENSTIIVE setting is simply ignored. Fixing this may entail just a doc change or a comment in mkdirs.cfg to indicate that CASE_SENSITIVE setting is ignored on OSX. That's fine since OSX isn't an officially supported platform for the SDP, despite it commonly being used for testing. Component: init Type: Bug