The /p4/common/site directory is to be used as a standard location for storing any custom or site-specific files that are not part of the SDP package that comes from Perforce Software. The automated SDP upgrade procedure knows to ignore the /p4/common/site directory tree. The standard SDP shell environment mechanism includes /p4/common/site/bin in the PATH, so that adding executable files in there will put them in the PATH and thus make them easily accessible. Files in the /p4/common/site tree are inherently custom and site-local, and as such are not supported by Perforce Support.
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #3 | 31204 | Will Kreitzmann |
Released SDP 2024.2.31193 (2025/01/17). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #2 | 29891 | C. Thomas Tyler |
Released SDP 2023.1.29699 (2023/07/11). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #1 | 27331 | C. Thomas Tyler |
Released SDP 2020.1.27325 (2021/01/29). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| //guest/perforce_software/sdp/dev/Server/Unix/p4/common/site/bin/ReadMe.txt | |||||
| #1 | 26932 | C. Thomas Tyler |
Repurposed the /p4/common/site directory. This directory will exist on a a fresh SDP install, but will be empty save for a ReadMe.txt file explaining that it is to be used to make local extensions to the SDP, and that anything in here is not supported. The coming automated SDP upgrade procedure will know to ignore /p4/common/site directory tree. The p4_vars ensures that /p4/common/site/bin is in the PATH. |
||