RTC SCM retain execute bits for checkin files?
I am having issues with RTC SCM removing/stripping the execute bit from my ruby and perl source files. Can i get RTC to retain the execute bit for files checked into RTC? Also, would this behavior be support across different platforms like Windows and UNIX. Since Windows doesn't really not about the execute bit, would it strip it or just ignore it, so my Linux developers don't loose this.
Right now my workaround is to put the execute bit back on the files individually or with a script.
Right now my workaround is to put the execute bit back on the files individually or with a script.
2 answers
Hi Robert, there is an issue with the load operation stripping this bit. This is being tracked in the following workitem which is not yet implemented.
UNIX File Permissions Aren't Maintained After scm load... (161875)
I'd suggest voting up the RFE's mentioned in comment 27 in the RFE community. These are official requests that have SLA's which development and product management are required to update\respond to within certain time frames.
UNIX File Permissions Aren't Maintained After scm load... (161875)
I'd suggest voting up the RFE's mentioned in comment 27 in the RFE community. These are official requests that have SLA's which development and product management are required to update\respond to within certain time frames.
