<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 21, 2010, at 3:10 PM, keith wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div><blockquote type="cite"><font class="Apple-style-span"><br></font></blockquote><blockquote type="cite">Very good. Is it the same simpler traits as pharo?<br></blockquote><br><br>What's your point?</div></blockquote><div><br></div><div>I write and maintain packages for users in both squeak and pharo, surely my point is obvious, </div></div></div></blockquote><div><br></div><div><br></div>No, it was not obvious. Even upon rereading, it doesn't seem like you're conceding that your statement that the process "can only build a monolithic image" is mistaken... it seems like you're trying to change the subject.</div><div><br></div><div><br></div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>I don't want extra work, and I dont want to have to maintain separate code bases.<span class="Apple-tab-span" style="white-space:pre"> </span></div></div></div></blockquote><div><br></div><div><br></div><div>Fair enough. I believe that Andreas went to some lengths to maintain compatibility.</div><div><br></div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div> I was just hoping for a simple answer, "yes" would be good. I wasn't being cynical, I was just interested to know.</div></div></div></blockquote><div><br></div><div><br></div>I apologize for my misunderstanding. I believe the answer is no.</div><div><br></div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><br></div><blockquote type="cite"><div> I responded to your false statement that the process "can only build a monolithic image". I'm not talking about cross-fork compatibility here.<font class="Apple-style-span"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><br></div><div>I can unload packages from any image with Sake/Packages, I dont need the trunk process for that, but lets see your process build an image without Monticello, or with Morphic3, or Rio instead of FileDirectory.</div></div></blockquote><div><br></div><div><br></div><div>I never claimed that the trunk process is necessary for package unloading. You're the one who claimed that the trunk process can only build a monolithic image, and I debunked it with a counter-example. </div><div><br></div><div>I realize that you're responding to emails from many people, but let's please try to follow the argument, otherwise we're all wasting our time.</div><div><br></div><div><br></div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Basically you are not able to offer anything fundamentally different from what has gone before, </div></div></blockquote><div><br></div><div><br></div>In terms of unloading packages, maybe not (are you now admitting that real progress has been made in that regard?). But in terms of pace of development, obviously so.<div><br></div><div><br></div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I don't want File/Directory in my image I hate it with a passion. My entire motivation for hacking the core in the first place is to get rid of FileDirectory.</div></div></blockquote><div><br></div><div><br></div>Gaaah. No argument there.</div><div><br></div><div>Cheers,</div><div>Josh</div><div><br></div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>"Fail to plan plan to fail", I think the saying goes.</div><div><br></div><div>Keith</div></div><br></blockquote></div><br></body></html>