As I understand it, you are supposed to be able to specify which package can perform whatever functions you give them rights to. So I made the following entry:
I have a command in the ..\commands\test directory which needs access to the POL root directory to create a folder there and write cfg files in it. However with the above entry the command can create the directory but it can't create any files in the directory. If I change the entry in fileaccess.cfg to:


It works but I'd rather not give universal access for cfg file creation.

So the question is: Am I doing something wrong or is this a bug (feature ) of POL?

Mmmh can you post the content of the pkg.cfg where the command exists in?

Here's the pkg.cfg. It's pretty much copied from Austin's 0.96 or 0.97 Distro. Now the actual command lives in a subdirectory, 'test', under the 'commands' directory but none of the subdirectories there contain any pkg.cfg files.

Nothing new on this yet Turley?

Sorry I'm currently working for 2 weeks in Japan. I think I have to test it myself to understand the problem. Currently it's a bit unclear why this happens, maybe a bug in the core or we oversee something.

How can you let work get in the way of POL?

Ok. It's not a showstopper bug for me because I only need to have access to the folder for a one time script. Then I can remove the file access rights but I thought you should be aware of it.

If I remember correctly, you also can define a Directory for the Fileaccess. By default it only allows inside the package you named...

Could you check if that's the case?

I can but with the wildcard * in the Package element it worked with a Directory element. Will get back to you with a report.

Oh, sorry. I just checked the code: the Directory flag is not implemented yet. I'll have to look into it with more time later...

Now that you mention it I remember seeing that comment in the fileaccess.cfg file.

Maybe this should be looked at and fixed if possible before we finalize POL 0.99.