<div dir="ltr">I spoke with Steve Langasek about this a bit ago and the solution he mentioned was to convert your deb package into basically a stub package that prints a debconf note guiding the user to install the updated apps via `snap install`.</div><br><div class="gmail_quote"><div dir="ltr">On Thu, Aug 18, 2016 at 7:38 AM Mark Shuttleworth <<a href="mailto:mark@ubuntu.com">mark@ubuntu.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Policy for non-core apps is that newer versions should be provided as<br>
snaps, LTS-released versions should be maintained as debs (but not<br>
updated to newer versions).<br>
<br>
By non-core I mean anything that is not in the ubuntu-core snap.<br>
<br>
By apps I mean things that would make a natural snap or (in the case of<br>
libraries) snapcraft part.<br>
<br>
So Marco is exactly right to ask this question now, since we need to<br>
evolve a best practice for how to socialize that there is a newer<br>
version of the software available as a snap.<br>
<br>
Mark<br>
<br>
<br>
--<br>
Snapcraft mailing list<br>
<a href="mailto:Snapcraft@lists.snapcraft.io" target="_blank">Snapcraft@lists.snapcraft.io</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snapcraft" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snapcraft</a><br>
</blockquote></div>