<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><pre class="">>It's all here:
> <a href="http://wiki.squeak.org/squeak/6365" class="">http://wiki.squeak.org/squeak/6365</a>
>This is what <a href="http://source.squeak.org" class="">source.squeak.org</a> is running. It installs and runs clean
>(in Linux). It never saves the running image.
>Every serious Squeak developer should do it on their laptop, so they
>can have the revision history for their own proprietary code, not just
>the <a href="http://source.squeak.org" class="">source.squeak.org</a> repositories.</pre><div class=""><br class=""></div><div class="">This is interesting, but it seems over engineered. Http was never part of the first, second or third designs of Monticello. It went large when people in Bern made SqueakSource. The aim, I think, was to present the packages in an HTML format for people to read instead of having a faceless HTTP address access to a file directory somewhere. After that, it seems, people forgot Monticello has ten different kinds of repository available.</div><div class=""><br class=""></div><div class="">With the instructions I’ve shown below, I think a person could do what you’re doing after five minutes of setup using only Monticello in an any image. [1] And it would work on any OS, not just Linux. Getting Installer scripts to point to a directory on your desktop (simultaneously copying into Dropbox perhaps?) would be a next and probably simple step. </div><div class=""><br class=""></div><div class="">All the code history is in the MC files on disk. I don’t think SqueakSource has anything to say about your versions. I don’t think you need SqueakSource at all. Just Monticello. Is there something here I’m missing? </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Chris </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">[1] </div><div class="">1 Create a desktop folder called “MyMonticelloFiles” </div><div class="">2 In MC add as a directory repository pointing to MyMonticelloFiles</div><div class="">3 Existing packages in MC won’t see the new repo from “add repository”, until…</div><div class="">4 Go to Browser. Put any class in a new class category (i.e. MCDummyCategory)</div><div class="">5 Add new package “MCDummyCategory” in MC</div><div class="">6 “Add Repository” for MCDummyCategory to MyMonticelloFiles repository</div><div class="">7 Save MCDummyCategory to MyMonticelloFiles on disk</div><div class="">8 All existing packages now have MyMonticelloFiles as a destination</div><div class="">9 Adapt Installer script to use “Installer monticello directory: ‘MyMonticelloFiles’ or something</div><div class="">Details here, I suppose. <a href="http://installer.pbworks.com/w/page/19997682/Installer" class="">http://installer.pbworks.com/w/page/19997682/Installer</a> </div></body></html>