Question/Request: Directory for data that should persist over updates.

Kyle Fazzari kyle.fazzari at
Fri Jan 29 14:54:30 UTC 2016

On 01/29/2016 09:47 AM, John Lenton wrote:
> On 28 January 2016 at 18:12, Jamie Strandboge <jamie at> wrote:
>> Currently SNAP_DATA and SNAP_USER_DATA are versioned, so putting it as
>> a fixed directory there is possible but likely messy. Unless I'm
>> missing some important details, it seems a separate directory and
>> envvar is the cleanest.
> Yep, with you on this one.

I agree, though I also feel like SNAP_DATA and SNAP_USER_DATA are in
logical locations (/var/lib/snaps/<package name>/ and
$HOME/snaps/<package name>, respectively). What would be a
similarly-logical scheme for unversioned data? Perhaps an option is to
nest one more level: /var/lib/apps/<package name>/versioned/ would
become the current, versioned SNAP_DATA and /var/lib/apps/<package
name>/unversioned for the unversioned one. Similar type of thing for
SNAP_USER_DATA. Or something similar.

Then again... that might break snaps with hard-coded paths to the
`current` symlink.

Kyle Fazzari (kyrofa)
Software Engineer
Canonical Ltd.
kyle at

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the snappy-devel mailing list