| problems with chmod touchpoint action [message #114078] |
Mon, 14 July 2008 16:33  |
 Ryan Mising name
Messages: 9
Registered: July 2009 |
Junior Member |
|
|
I am trying to use the chmod touchpoint action on the install phase for my
plug-in, and I can't get it to work quite right. It works fine for
something simple like changing the permissions of one file:
<instruction key='install'>
chmod(targetDir:${installFolder}/path/to/file,targetFile:myF ile,permissions:+x);
</instruction>
But when I try to recursively set permissions on a directory, like I would
with "chmod -R +x myDirectory/", it does not work:
<instruction key='install'>
chmod(targetDir:${installFolder}/path/to/parentDirectory,tar getFile:myDirectory,permissions:-R
+x);
</instruction>
I have also tried putting the "-R +x" in double quotes and single quotes,
nothing works. I have also tried specifying * for targetFile just to see
if that would work, and that doesn't even seem to work.
What's the deal? chmod'ing a directory or files is one of the most common
uses of install handlers...how are we supposed to migrate our plug-ins to
p2 if it won't work? Hopefully I'm doing something wrong...
As an aside, could you have made p2 a little more complicated? My
frustration is growing by the day...
- Ryan
|
|
|
| Re: problems with chmod touchpoint action [message #114086 is a reply to message #114078] |
Mon, 14 July 2008 20:33  |
Simon Kaegi
Messages: 381
Registered: July 2009 |
Senior Member |
|
|
Hi Ryan,
Hmm... my guess is that the relevant chunck of the chmod call is being
interpreted as:
'-R +x' instead of as '-R' and '+x'.
Please open a bug as the chmod action should parse out the space and report
the error better. If you feel like figuring out what is going on you can set
a breakpoint in
org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.C hmodAction line
57
-Simon
"Ryan" <huffrg3@gmail.com> wrote in message
news:6fdda410f628357e946736e0869b7975$1@www.eclipse.org...
>I am trying to use the chmod touchpoint action on the install phase for my
>plug-in, and I can't get it to work quite right. It works fine for
>something simple like changing the permissions of one file:
>
> <instruction key='install'>
>
> chmod(targetDir:${installFolder}/path/to/file,targetFile:myF ile,permissions:+x);
> </instruction>
>
> But when I try to recursively set permissions on a directory, like I would
> with "chmod -R +x myDirectory/", it does not work:
>
> <instruction key='install'>
>
> chmod(targetDir:${installFolder}/path/to/parentDirectory,tar getFile:myDirectory,permissions:-R
> +x);
> </instruction>
>
> I have also tried putting the "-R +x" in double quotes and single quotes,
> nothing works. I have also tried specifying * for targetFile just to see
> if that would work, and that doesn't even seem to work.
>
> What's the deal? chmod'ing a directory or files is one of the most common
> uses of install handlers...how are we supposed to migrate our plug-ins to
> p2 if it won't work? Hopefully I'm doing something wrong...
>
> As an aside, could you have made p2 a little more complicated? My
> frustration is growing by the day...
>
> - Ryan
>
|
|
|
Powered by
FUDForum. Page generated in 0.02571 seconds
] 
Search
Help
Register
Login
Home
