<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    On 8/9/2020 9:36 PM, Phil B via Cuis-dev wrote:
    <blockquote
cite="mid:CAMJMOehCDM65A2gk0firBy3-ii7tChHQNCUkqh4S50iD+e6R0w@mail.gmail.com"
      type="cite">
      <div dir="ltr">The changeset asks the user if they want to
        reload.  The issue is the act of reloading a package: it's
        inherently unsafe.</div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Sun, Aug 9, 2020 at 7:55 PM
          Mariano Montone via Cuis-dev <<a moz-do-not-send="true"
            href="mailto:cuis-dev@lists.cuis.st">cuis-dev@lists.cuis.st</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin: 0px 0px 0px
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">El 9/8/20 a las 20:09, Phil B via Cuis-dev
          escribió:<br>
          > I think this is a good idea conceptually, dangerous in
          practice.  The<br>
          > update changesets are intended to be installed one after
          the other on<br>
          > top of each other, packages aren't.  I'd bet that no one
          ever does any<br>
          > testing to see if installing a new package over an older
          one works<br>
          > correctly.<br>
          <br>
          Perhaps you could warn the user, and Object>>confirm:
          the operation.<br>
          -- <br>
          Cuis-dev mailing list<br>
          <a moz-do-not-send="true" href="mailto:Cuis-dev@lists.cuis.st"
            target="_blank">Cuis-dev@lists.cuis.st</a><br>
          <a moz-do-not-send="true"
            href="https://lists.cuis.st/mailman/listinfo/cuis-dev"
            rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a><br>
        </blockquote>
      </div>
    </blockquote>
    <br>
    Phil, what you say is true. We could instead check package versions
    and inform the user which packages could / should be reloaded.<br>
    <br>
    Still, we can say that loading numbered updates to the core image is
    only safe if the image has no packages or user code loaded (i.e. it
    is unmodified in any way since downloaded), as this is the only case
    that we test.<br>
    <br>
    Thanks,<br>
    <pre class="moz-signature" cols="72">-- 
Juan Vuletich
<a class="moz-txt-link-abbreviated" href="http://www.cuis-smalltalk.org">www.cuis-smalltalk.org</a>
<a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a>
<a class="moz-txt-link-freetext" href="https://github.com/jvuletich">https://github.com/jvuletich</a>
<a class="moz-txt-link-freetext" href="https://www.linkedin.com/in/juan-vuletich-75611b3">https://www.linkedin.com/in/juan-vuletich-75611b3</a>
@JuanVuletich</pre>
  </body>
</html>