Can't we do something more elegant than that? Having to implement
wrappers and or code changes to each and every program with hardcoded
values seems overly painful.
Couldn't we do something fancy/smart with system calls such that fopen
prepends $SNAP to most requests? I can't imagine there being more than
a few system calls that would need to be modified.
I also realize that it would take more work than this simplistic
suggestion, but has anyone researched something like that? Plus it
would give each application even better isolation since the isolation
would be enforced by snappy.
On 09/16/2016 03:55 AM, Oliver Grawert wrote:
> Am Donnerstag, den 15.09.2016, 16:10 -0500 schrieb Dave Chiluk:
>> Hey guys, I'm trying to snap up file. I thought it would be simple.
>> This is what I have for my snapcraft.yaml.
>> However when I go to run file out of my snap I get
>> chiluk@localhost:~$ file /home/chiluk/file_0_amd64.snap
>> /etc/magic, 0: Warning: using regular magic file
>> file: could not find any valid magic files!
> you will need a wrapper ... make it call file -m and point to the $SNAP
> location of the magic file:
> (from the manpage)
> -m, --magic-file magicfiles
> Specify an alternate list of files and directories
> containing magic. This can be a single item, or a colon-separated
> list. If a compiled
> magic file is found alongside a file or directory, it will
> be used instead.
Snapcraft mailing list
Modify settings or unsubscribe at: