Gábor Paller gaborpaller at
Sun Nov 1 09:11:08 UTC 2015

" (I don't recall the bugs, but they're in launchpad
if you care to look for them)."

Now you got another surprising behaviour.
Let's say you have a snap called "mysnap" and it has a 'bin' directory,
containing the executable "prog".
Deploy the snap, go into /apps/mysnap.sideload/current/bin and execute
Now update "prog", redeploy, and execute "prog" again.
Surprise, surprise, it is the old one. Because your shell remained in a
directory that was "current" at certain point but it is
not anymore. In order to get the redeployed package, you have to cd
/apps/mysnap.sideload/current/bin again.

On Sat, Oct 31, 2015 at 1:16 AM, John Lenton <john.lenton at>

> On 30 October 2015 at 21:31, Gábor Paller <gaborpaller at> wrote:
> > and why is the difference?
> because most of the times developers will install the same package
> again and again while building and debugging their program, and that
> breaks some things (I don't recall the bugs, but they're in launchpad
> if you care to look for them). We had two options: stop developers
> from being able to re-sideload things with the same declared version,
> or override it.
> Given that the path to a package should not be relied on for anything
> (this is why you get all those useful environment variables), and will
> at some point probably go away in favour of store revisions even for
> store-installed packages, it seemed like the best option.
> --
> snappy-devel mailing list
> snappy-devel at
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the snappy-devel mailing list