snapd

No 'current' symlink for $SNAP_USER_DATA

Bug #1638248 reported by Stuart Bishop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Triaged
High
Unassigned

Bug Description

There is a 'current' to the current $SNAP_DATA which is very useful (/var/snap/mysnap/current -> /var/snap/mysnap/42), as that path can be used to add or edit contained datafiles from outside containment, without worrying about too much about snap updates happening simultaneously and changing the paths.

There is no equivalent for $SNAP_USER_DATA. Can we have one please?

Revision history for this message
Stuart Bishop (stub) wrote :

This is a particular problem if you need absolute paths to any data files. I've just needed to workaround this issue by using $SNAP_USER_COMMON and requiring manual cleanup if the snap gets reverted, because I need to store absolute paths to files in the applications configuration.

Michael Vogt (mvo)
Changed in snappy:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Paweł Stołowski (stolowski) wrote :

Here is the PR for this: https://github.com/snapcore/snapd/pull/2515

Michael Vogt (mvo)
affects: snappy → snapd
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.