El 04/03/16 a las 13:03, Gustavo Niemeyer escribió: > > On Fri, Mar 4, 2016 at 1:01 PM, Didier Roche <didro...@ubuntu.com > <mailto:didro...@ubuntu.com>> wrote: > > So, they will probably either use: > $SNAP/<path_to_asset_or_helper> > > > To be fair, that argument goes both ways. They might just as well do > $SNAP_DATA/<path to data>.
I am very late to this thread, but it seems all apps default to SNAP_DATA?
ubuntu@localhost:~$ hello-world.env | grep '^PWD='
PWD=/var/lib/snaps/hello-world.canonical/6.0
Why not SNAP_USER_DATA? As a user I cannot do anything on SNAP_DATA
unless I sudo, if that were the case I'd prefer the current PWD to be
preserved so at least I know where I am.
So in my busybox snap I cannot do (unless I sudo):
ubuntu@localhost:~$ busybox.touch touched_file
I cannot do this either (as the envvar for obvious reasons does not exist):
ubuntu@localhost:~$ busybox.touch $SNAP_USER_DATA/touched_file
If it is the current working directory I could at least change dir to
whatever location I could write to before executing this `busybox.touch`
command.
If it were a daemon I have no quarrel with SNAP_DATA being the working
directory though.
Can we revert this behavior?
signature.asc
Description: OpenPGP digital signature
-- snappy-devel mailing list snappy-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
