<p dir="ltr">Hi,</p>
<p dir="ltr">In the case of installing snaps from the local file system, where will the assertions require to installation reside? Also in the local file system?</p>
<p dir="ltr">I can see this use case when either the snap is not yet in the store (during development) or the device has no access to the/a store (maybe behind a firewall)</p>
<p dir="ltr">Thanks </p>
<p dir="ltr">Victor </p>
<p dir="ltr">Thanks </p>
<p dir="ltr">Victor </p>
<div class="gmail_extra"><br><div class="gmail_quote">On Sep 2, 2016 8:08 AM, "Oliver Grawert" <<a href="mailto:ogra@ubuntu.com">ogra@ubuntu.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi,<br>
Am Donnerstag, den 01.09.2016, 19:15 -0300 schrieb Gustavo Niemeyer:<br>
> Hello all,<br>
><br>
> With assertions finally being put to great use, it's time to kill the<br>
> term "sideloading". That term does a disservice to our conversations,<br>
> because it is vague and also limits the thinking around what is<br>
> possible.<br>
><br>
> Whenever we use "sideloading", we mean one of two things:<br>
><br>
does it actually matter what *we* use ? its the slang of the android<br>
kids, it is what they know and will use when talking about the topic of<br>
installing local packages, no matter what we say in our marketing docs<br>
... <br>
<br>
i dont mind changing it in docs or watching my personal language to not<br>
use it if we decide on a term, but i doubt the crowd will follow if you<br>
dont find a term that feels like a natural replacement for them...<br>
<br>
ciao<br>
oli<br>
<br>
<br>--<br>
Snapcraft mailing list<br>
<a href="mailto:Snapcraft@lists.snapcraft.io">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/<wbr>mailman/listinfo/snapcraft</a><br>
<br></blockquote></div></div>