ubuntu-phone team mailing list archive

[Robert Schroll <rschroll@xxxxxxxxx>]

On Thu, Feb 19, 2015 at 3:49 PM, Jamie Strandboge <jamie@xxxxxxxxxxxxx> 
wrote:
> # LP: #1293771
> # Since fd delegation doesn't exist in the form that we need it at 
> this time,
> # content-hub will create hard links in 
> ~/.cache/@{APP_PKGNAME}/HubIncoming/
> # for volatile data. As such, apps should not have write access to 
> anything in
> # this directory otherwise they would be able to change the source 
> content.
> deny @{HOME}/.cache/@{APP_PKGNAME}/HubIncoming/** w,

Does this explain why the move() method doesn't actually work, and has 
to fall back to a copy?  If so, why try to rename the file when we know 
that it can't possibly work?

I'm guessing from the comment that the cache will be cleaned out 
occasionally, so I need to copy the content into my silo if I want to 
be able to access it again later.  Is that correct?

Since I can't actually share the file with another app, is there any 
way to get notified when the original file gets modified or deleted?

Let me repeat some of my original questions that are still relevant:

4) Is the argument to move() relative to some directory, or must I use 
an absolute path?  Is there any abbreviation for $HOME? (~ doesn't seem 
to work.)

6) Is there anyway to tell that two imports are actually the same 
original file?   Short of running md5sum on them, I mean.  The filename 
in HubIncoming seems to be the same as the original file.  Is that 
guaranteed?

Maybe I'm being unusually dense, but I'm having trouble understanding 
how this is supposed to be used for long-term file management, as 
opposed to a quick send-this-picture-in-an-email usage.

> Note: an explict deny rule suppresses the denial in the logs

This hasn't tripped me up yet, but in general, I find apparmor problems 
hard to diagnose.  (Qt says the directory is writable, but I can't make 
an files in there.)  Why suppress the log message and make it even more 
mysterious?

Thanks for the help,
Robert