|
Re: Preserving file permissions in exported features [message #487548 is a reply to message #487034] |
Wed, 23 September 2009 14:57 |
Chris Aniszczyk Messages: 674 Registered: July 2009 |
Senior Member |
|
|
Peter Saunders wrote:
> Hi
>
> I need to include some native Linux executable files within an Eclipse
> 3.5 plug-in. When I generate an update site for the feature containing
> this plug-in, the executable file permissions are lost. I'm looking for
> the simplest way to preserve these file permissions. Searching various
> discussion archives, it seems that it should be possible to force the
> generation of tar files rather than zip files by adding the following
> line to build.properties in the feature project:
>
> archivesFormat=win32, win32, x86 - zip & linux, gtk, x86 - tar
How are these executables shipped? Within a feature? Are they rootfiles?
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .pde.doc.user/tasks/pde_rootfiles.htm
If they are root files, there are properties you can set to change
permissions, i.e:
root.permissions.755=eclipse: Set the 'eclipse' file to have executable
permissions.
root.linux.gtk.x86.permissions.755=lib/**: Set all files under the lib
directory to be executable
See the documentation in the link above.
Cheers,
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
|
|
|
Re: Preserving file permissions in exported features [message #487810 is a reply to message #487548] |
Thu, 24 September 2009 13:40 |
Peter Saunders Messages: 30 Registered: July 2009 |
Member |
|
|
Hi Chris
Thanks for your reply.
You wrote:
>> Peter Saunders wrote:
>>
>> I need to include some native Linux executable files within an Eclipse
>> 3.5 plug-in. When I generate an update site for the feature containing
>> this plug-in, the executable file permissions are lost. I'm looking for
>> the simplest way to preserve these file permissions. Searching various
>> discussion archives, it seems that it should be possible to force the
>> generation of tar files rather than zip files by adding the following
>> line to build.properties in the feature project:
>>
>> archivesFormat=win32, win32, x86 - zip & linux, gtk, x86 - tar
>
> How are these executables shipped? Within a feature? Are they rootfiles?
I am flexible, but I do need this to work with an Eclipse update site.
> If they are root files, there are properties you can set to change
> permissions, i.e:
>
> root.permissions.755=eclipse
> root.linux.gtk.x86.permissions.755=lib/**
This looks like a good option for me. I have experimented with defining rootfiles within an Eclipse feature project and it is mostly working. I can deliver my executable files within a hierarchy of directories and ensure that file permissions are set correctly. But when I UNinstall the feature which provides these files, I am left with a hierarchy of empty directories under the rootfile directory. Perhaps the rootfile uninstall code cannot handle subdirectories. Is this a known problem?
Peter Saunders
|
|
|
|
|
Re: Preserving file permissions in exported features [message #601937 is a reply to message #487548] |
Thu, 24 September 2009 13:41 |
Peter Saunders Messages: 30 Registered: July 2009 |
Member |
|
|
Hi Chris
Thanks for your reply.
You wrote:
>> Peter Saunders wrote:
>>
>> I need to include some native Linux executable files within an Eclipse
>> 3.5 plug-in. When I generate an update site for the feature containing
>> this plug-in, the executable file permissions are lost. I'm looking for
>> the simplest way to preserve these file permissions. Searching various
>> discussion archives, it seems that it should be possible to force the
>> generation of tar files rather than zip files by adding the following
>> line to build.properties in the feature project:
>>
>> archivesFormat=win32, win32, x86 - zip & linux, gtk, x86 - tar
>
> How are these executables shipped? Within a feature? Are they rootfiles?
I am flexible, but I do need this to work with an Eclipse update site.
> If they are root files, there are properties you can set to change
> permissions, i.e:
>
> root.permissions.755=eclipse
> root.linux.gtk.x86.permissions.755=lib/**
This looks like a good option for me. I have experimented with defining rootfiles within an Eclipse feature project and it is mostly working. I can deliver my executable files within a hierarchy of directories and ensure that file permissions are set correctly. But when I UNinstall the feature which provides these files, I am left with a hierarchy of empty directories under the rootfile directory. Perhaps the rootfile uninstall code cannot handle subdirectories. Is this a known problem?
Peter Saunders
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04138 seconds