Application cwd in SNAP_APP_PATH vs SNAP_APP_DATA_PATH

[Gustavo Niemeyer]

Well, one can "work" anywhere really. The analogy with $HOME is
interesting, for example, because one doesn't usually write in $HOME
itself, but rather creates a per-application directory and writes into that
instead. So very similar.
That said, countering my own point there's the argument that there's
nothing useful one can do with CWD being $SNAP, I think?

So it'd probably be fine with changing it to $SNAP_DATA too, as a default.
People will find out about $SNAP_USER_DATA when they need to.


On Mar 4, 2016 12:25 PM, "Mark Shuttleworth" <mark at ubuntu.com> wrote:

> On 03/03/16 21:59, Didier Roche wrote:
> > Discussing with Michael yesterday, it seems that this wasn't really
> > discussed in the past and may be a good change for 16.04 for the big
> > cleanup time :)
> > I was first surprised to see that when starting an application, the
> > current directory was SNAP_APP_PATH.
> >
> > In traditional systems, the current directory is generally a path where
> > the app have write access to (like $HOME or the one your are in for CLI).
> > I realize that in most of the snappy apps/services I'm writing, I'm
> > doing `cd $SNAP_APP_DATA_PATH` as first thing in most of them.
> >
> > In that case, is there any particular reason to set the current working
> > directory to SNAP_APP_PATH instead of SNAP_APP_DATA_PATH or would a
> > change to set it to the latter makes sense for 16.04?
>
>
> Makes sense to me that the current working directory should be a place
> one can work :)
>
> Mark
>
> --
> snappy-devel mailing list
> snappy-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snappy-devel
>


-- 
gustavo @ http://niemeyer.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20160304/55635a7d/attachment.html>