packager: access rights

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.

Alain Bonnefoy wrote:

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?

Alain, just a guess, but perhaps the permissions are copied
from those of the source directory you used when creating
the package.

Regards
William Morris

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:

after package installation, I can see the following message:
/VA01109-1 not supported.

welcome to the world of fs-pkg :slight_smile:

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.

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.



\

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.

Hi Andrew,

Andrew Scheel a écrit:

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.

This is what I noticed.



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.


Unfortunately not, you cannot do anything to a directory belonging to

fs-pkg!
This is why my post-install script returned ‘not supported’ on chmod.

I was waiting for Jerry but…

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.





\

← Snip →

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.


Unfortunately not, you cannot do anything to a directory belonging to
fs-pkg!
This is why my post-install script returned ‘not supported’ on chmod.

Oh I see now that you don’t create the directory in question. I

misunderstood. Maybe Jerry will have a solution. As I dont have one for you
at present. Sorry I coundn’t help more. A bug will be logged on your behalf.

-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.






\

I suppose Jerry is in vacation!

Alain.
Andrew Scheel a écrit:

– Snip –


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.




Unfortunately not, you cannot do anything to a directory belonging to
fs-pkg!
This is why my post-install script returned ‘not supported’ on chmod.



Oh I see now that you don’t create the directory in question. I
misunderstood. Maybe Jerry will have a solution. As I dont have one for you
at present. Sorry I coundn’t help more. A bug will be logged on your behalf.

-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.











\

Alain, I’m here and I’ve been watching the thread. Unfortunately, I don’t
have an answer for you yet.

Is the directory you’re creating defined in any other package, or is this a
directory just for your pacakge?

Jerry

I’ve been watching this thread too, and one thing I didn’t
understand was why it wasn’t possible in this instance just
to chmod the “real” files/directories deep down under
/pkgs/repository or wherever. I’ve occasionally done that
myself. Maybe there was something about the requirements I
missed in this case…

dB


“Jerry Chappell” wrote, ca. Wed, 19 Mar 2003 09:02:48 -0500:

Alain, I’m here and I’ve been watching the thread. Unfortunately, I don’t
have an answer for you yet.

Is the directory you’re creating defined in any other package, or is this a
directory just for your pacakge?

Jerry

Alain, I’ve confirmed that this is a behaviour that is lacking from
packager. ie: there is no way to do what you’re trying to do using packager.
I’ll try to add a workaround for the next release, but unfortunately there’s
simply no way to do it at this time.

Sorry.
Jerry

“Jerry Chappell” <jchappell@qnx.com> wrote in message
news:b59t5c$dm8$1@nntp.qnx.com

Alain, I’m here and I’ve been watching the thread. Unfortunately, I don’t
have an answer for you yet.

Is the directory you’re creating defined in any other package, or is this
a
directory just for your pacakge?

Jerry

Ok, David I’m going going to make it clear, it will be usefull for Jerry
also in order he thinks about its workaround (even if I don’t consider
that as a workaround!).
My package creates a collection of files an executables located in a
‘/VA01109-1’ directory right?
So, strictly speaking about the files there is no problem to specify
their access rights.
The problem is, when you create your files with the following tag:

<QPG:Add file=“database_files/CP_STD.dat”
install="/VA01109-1/ds/" permissions=“666”/>

you don’t explicitly create the ‘/VA01109-1’ directory and you don’t
have any possibilities to define it’s access rights AFAIK!

So, if your application or anything else needs to create some files in
that dir and don’t have root rights, it can’t!

I tried to create the directory first with the good rights but when the
package is going to be installed, it doesn’t use the existing dir but
creates its own one, even if it dosesn’t change anything in it, (already
existing files).
I wonder if it’s really necessary as it points to the same disk location.

Thanks,
Alain.
David Bacon a écrit:

I’ve been watching this thread too, and one thing I didn’t
understand was why it wasn’t possible in this instance just
to chmod the “real” files/directories deep down under
/pkgs/repository or wherever. I’ve occasionally done that
myself. Maybe there was something about the requirements I
missed in this case…

dB


“Jerry Chappell” wrote, ca. Wed, 19 Mar 2003 09:02:48 -0500:

Alain, I’m here and I’ve been watching the thread. Unfortunately, I don’t
have an answer for you yet.

Is the directory you’re creating defined in any other package, or is this a
directory just for your pacakge?

Jerry