Just a little typo there… .epg should be .qpg…
Robert your right it should work this way and it is the proper way to set
permisions. However, after doing a few tests I’ve found that this is a short
comming in packager (aka Bug). The 'type=“tree” file=“dir”
permissions=“777”'options are only working for files at this point. I tried
to find a work around but could not. The only way I can think to do it at
this point is to change the permisions on the dir before you package and
then change them back within a script.
Thanks for bring this to our attention.
-Andrew
“Alain Bonnefoy” <alain.bonnefoy@icbt.com> wrote in message
news:3E75D981.8090706@icbt.com…
unfortunately no!
Don’t know if it should work but it doesn’t!
regards,
Alain.
Robert Rutherford a écrit:
In your .epg file, you can specify the desired permissions after
installation. Doing a chmod in a post-install script is bad: it will cause a
file to be spilled and won’t work at all on a directory.
Something like
<QPG:Add type=“tree” file="…" owner=“whoever” group=“whatever”
permissions=“755” />
In your Options section your will also need
<QPG:FileSorting ownership=“override” />
Hope this helps,
Rob Rutherford
“Alain Bonnefoy” <alain.bonnefoy@icbt.com> wrote in message
news:3E7042FF.1020407@icbt.com…
Hi,
I have a package which creates some files as:
/VA01109-1/file1
/VA01109-1/file2
…
access rights about files are ok, no problem to set what I want.
The problem is about the /VA01109-1 directory for which the rights are
rwxr-xr-x. I’d like to set rwxrwxrwx.
So, I 've included a post install command ‘chmod a+w /VA01109-1’
after package installation, I can see the following message:
/VA01109-1 not supported.
I’m not really surprised by this message but how can I do to set access
rights for that directory as I don’t create it directly?
Thanks,
Alain.