<!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/10/2020 10:14 AM, Hilaire Fernandes via Cuis-dev wrote:
<blockquote cite="mid:8cbd98f0-4536-fa2b-3af8-ddd43c6eac66@drgeo.eu"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><font size="+1">The safe way will be to start from a fresh
image.</font></p>
<div class="moz-cite-prefix">Le 09/08/2020 à 23:21, Juan Vuletich
via Cuis-dev a écrit :<br>
</div>
<blockquote type="cite" cite="mid:5F3076FC.1060204@jvuletich.org">Today
I realized that if a Cuis user pulls the Cuis repo, and does
'Install 'New Updates' they might reasonable expect that any
installed packages are also updated. </blockquote>
<p>My bad there to make you suggest it is necessary.</p>
<p> Juan, your good will proposal try to take in consideration a
bad habits: keep working for days and weeks with an image with
external packages installed, then assuming doing an update on
this image will be safe. I remember you documented that an image
should never be saved: install packages, write code, save
packages, then throw away the image at the end of the day. While
working on DrGeo on Cuis, I follow this habit, and it is working
nicely. Only when experimenting with Vector graphics I keep the
image.</p>
<p>We should no forget to document it in The Cuis Book.<br>
</p>
<div class="moz-cite-prefix">Le 10/08/2020 à 01:36, Phil B via
Cuis-dev a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAMJMOehCDM65A2gk0firBy3-ii7tChHQNCUkqh4S50iD+e6R0w@mail.gmail.com">
<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>
</blockquote>
<pre class="moz-signature" cols="72">--
GNU Dr. Geo
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a></pre>
</blockquote>
<br>
I agree with you. Maybe a check and just a message to the user is
enough.<br>
<br>
WRT starting from a fresh image every day, I works for me. It also
leads me to review all the code I have in development, as I load it
again in a fresh image. Many times this leads to refactoring or
polishing. I think it is the "best practice" to advice adopting.<br>
<br>
But I also keep in mind that Cuis should also be comfortable for
long time Smalltalk users, who know what they are doing, and are
free to adapt the tools and work flow to what works best for them.
In general, I try to keep the "you should do it this way" to a
minimum.<br>
<br>
Still, giving sensible advice to those who want it, and rely on it
in order to trust the system, is a must.<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>