Hi,
Yes, it's a bug https://bugs.launchpad.net/snapd/+bug/1636934
Cheers,
Pawel
On 07.03.2017 19:38, Jian LUO wrote:
Hi list,
I found out that if a certain snap got removed, its configuration set by
snapctl is still accessible through 'snap get'. Is it a bug or a feature?
And if it's a featur
Hi, everyone.
We need a way to make "snap.yaml," hooks and, possibly, other stuff of our
gadget snap updateable.
The only way now I see is to provide a hook, which will download or get
files from the filesystem and replace files on the image by them, but such
a solution seem dangerous to me, beca
Hi Renat,
We are working on making parts of the gadget snap updatable for example, on
RPi, updating config.txt makes sense, but as you say this is a dangerous
area to be playing with as bricking the device is possible. Michael knows
more as he has be directly working on this lately.
Regards,
Jami
Thanks, Jamie.
The reason we need this feature is to deliver a product to out customers as
soon as possible
and then apply changes made in the rpi3 gadget snap as they become ready.
Best regards,
Renat
On Wed, Mar 8, 2017 at 1:06 PM, Jamie Bennett
wrote:
> Hi Renat,
>
> We are working on makin
Snaps have a much stronger sense of identity. They *own* /snap/foo and
that means you can build a much more predictable and reliable view of
their behavior. Versioning is a key part of the snap story, it gives the
user and the publiisher of the software a really *great* way to describe
what they a
Hey Mark,
thank you for explaining this, the reasons are clearer to me now.
> In the case of libraries and frameworks, you don't have to worry about
> persistent data that can or cannot be shared between the two versions.
> You would need to know the two paths of the two versions *anyway* in
> o
