file permissions
5 answers
Geoff:
Then what is the purpose of the Executable file property in the Jazz Source Control panel of the file properties dialog? I have the RTC 2.0 client installed on Linux, and when I chmod +x a file, RTC recognizes that the file permissions has changed and puts it into my pending changes view as unresolved. After delivering this change I expected that when the file was extracted for a build (on Unix) that this bit would be set, but it was not. Is this file property for some other purpose?
Thanks,
Howard
This is not currently possible, but has been requested in work item
118445. Please feel free to add a comment to that work item to indicate
your interest/support.
Cheers,
Geoff
On 10/7/2010 12:38 PM, lmgray wrote:
Does jazz have a notion of file permissions (mode bits / ACL's)?
For example, we'd like to be able to have a file (script or binary)
be set to executable upon scm load into a local workspace and/or
have file permissions preserved when checked in and then later
loaded.
I agree with Howard's comment. Setting the jazz.executable property on a file should cause it to load it with execute bit set. I have tested with 3.0.1 and this doesn't seem to work. I think there is an enhancement pending that implements full-blown ACLs, but this could serve as a good interim solution.
I was answering the "file permissions" part of your question (which RTC
does not yet support). But it should support the "executable" flag. If
this isn't being set properly on a file in the file area, please file a bug.
How does one set this executable flag? I can view it by right-clicking on the file, Properties -> Jazz Source Control but there's no option to change it.
Also, Team -> Change File Properties does not have an "executable" option anywhere that I can see.
I was answering the "file permissions" part of your question (which RTC
does not yet support). But it should support the "executable" flag. If
this isn't being set properly on a file in the file area, please file a bug.
Cheers,
Geoff
On 12/12/2010 1:38 PM, hmckinney wrote:
does not yet support). But it should support the "executable" flag. If
this isn't being set properly on a file in the file area, please file a bug.
Cheers,
Geoff
On 12/12/2010 1:38 PM, hmckinney wrote:
Geoff:
Then what is the purpose of the Executable file property in the Jazz
Source Control panel of the file properties dialog? I have the RTC
2.0 client installed on Linux, and when I chmod +x a file, RTC
recognizes that the file permissions has changed and puts it into my
pending changes view as unresolved. After delivering this change I
expected that when the file was extracted for a build (on Unix) that
this bit would be set, but it was not. Is this file property for some
other purpose?
Thanks,
Howard
gmclemmwrote:
This is not currently possible, but has been requested in work item
118445. Please feel free to add a comment to that work item to
indicate
your interest/support.
Cheers,
Geoff
On 10/7/2010 12:38 PM, lmgray wrote:
Does jazz have a notion of file permissions (mode bits / ACL's)?
For example, we'd like to be able to have a file (script or binary)
be set to executable upon scm load into a local workspace and/or
have file permissions preserved when checked in and then later
loaded.
Geoff:
Then what is the purpose of the Executable file property in the Jazz Source Control panel of the file properties dialog? I have the RTC 2.0 client installed on Linux, and when I chmod +x a file, RTC recognizes that the file permissions has changed and puts it into my pending changes view as unresolved. After delivering this change I expected that when the file was extracted for a build (on Unix) that this bit would be set, but it was not. Is this file property for some other purpose?
Thanks,
Howard
Then what is the purpose of the Executable file property in the Jazz Source Control panel of the file properties dialog? I have the RTC 2.0 client installed on Linux, and when I chmod +x a file, RTC recognizes that the file permissions has changed and puts it into my pending changes view as unresolved. After delivering this change I expected that when the file was extracted for a build (on Unix) that this bit would be set, but it was not. Is this file property for some other purpose?
Thanks,
Howard
This is not currently possible, but has been requested in work item
118445. Please feel free to add a comment to that work item to indicate
your interest/support.
Cheers,
Geoff
On 10/7/2010 12:38 PM, lmgray wrote:
Does jazz have a notion of file permissions (mode bits / ACL's)?
For example, we'd like to be able to have a file (script or binary)
be set to executable upon scm load into a local workspace and/or
have file permissions preserved when checked in and then later
loaded.
This is not currently possible, but has been requested in work item
118445. Please feel free to add a comment to that work item to indicate
your interest/support.
Cheers,
Geoff
On 10/7/2010 12:38 PM, lmgray wrote:
118445. Please feel free to add a comment to that work item to indicate
your interest/support.
Cheers,
Geoff
On 10/7/2010 12:38 PM, lmgray wrote:
Does jazz have a notion of file permissions (mode bits / ACL's)?
For example, we'd like to be able to have a file (script or binary)
be set to executable upon scm load into a local workspace and/or
have file permissions preserved when checked in and then later
loaded.