<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br><blockquote type="cite"><div>Honestly, what kind of automation you can invent here to migrate your<br>application from using package version A,<br>to package version B , which potentially, can be completely rewritten<br>from scratch?<br>You doomed to either stay with version A, or do a lot of manual work<br>migrating to version B and no magic tool will help you with that.<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><div><br></div><div>No automation at all is needed.</div><br><blockquote type="cite"><div>About cross-fork package development.<br><br>Each package having an environment-agnostic behavior , and environment<br>dependent.<br>The goal of developer is to identify these parts and connect them nicely.<br>But this is gone too far. It is now about defining and enforcing a<br>good practices in package development to avoid cross-dialect pitfalls.<br>How many packages we has built with cross-compatibility in mind?<br>How many packages having all globals declared in a single place, not<br>scattered among code?<br>And what automated tools can solve the problems, when your package<br>code using 'SmalltalkImage current' instead of 'Smalltalk'?<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><div><br></div><div>Again no automated tools.</div><div><br></div><div>I think you are getting hung up on the automated tools thing. Automation is nothing to do with this discussion.</div><div><br></div><div>I am not asking you or anyone to automate tools or anything.</div><div><br></div><div>I am asking you to use a process of thinking that documents what you do, in a way that enables it to be routinely harvestable. Its a process of knowledge capture. You can write it on paper if you like:</div><div><br></div><div>Example:</div><div><br></div><div>If you write me an explanation of how to install closures, it will be a lot easier to write if you say.... Start with a 3.10-release image. Do a,b,c,d,e and you will have a closures image, we shall call 3.10-closures.</div><div><br></div><div>As a trunk developer you cant write me this explanation. If you write me an explanation of how to install closures following trunk, it will be... Hmm when we did it we had this image that was hacked on by 10 people, so this is how I did a,b,c,d,e but I cant be sure that this will work for you. </div><div><br></div><div>that is the difference, and my example from the bazaar documentation clearly shows the difference</div><div><br></div><div>Keith</div><div><br></div></div></body></html>