<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jul 9, 2014 at 2:27 PM, Douglas McPherson <span dir="ltr"><<a href="mailto:djm1329@san.rr.com" target="_blank">djm1329@san.rr.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div>On Jul 9, 2014, at 11:11 , Chris Muller wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><a href="http://wiki.squeak.org/squeak/3324" target="_blank">http://wiki.squeak.org/squeak/3324</a><br></div><div class="gmail_extra"><br></div></blockquote><div><br></div><div>Thank you. I'll look into this.</div>
<div><br></div><div>Naturally I was hoping to provide a SqueakMap entry for the package, which IIUC can point to external repositories such as <a href="http://source.squeak.org" target="_blank">source.squeak.org</a>, <a href="http://squeaksource.com" target="_blank">squeaksource.com</a>, and ss3. But SqueakMap can also serve the files directly, is that correct?</div>
</div></div></blockquote><div><br></div><div>Yes.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div> If I use the .sar approach is it true that I would not be able to publish on ss3? I'm not saying that's a bad thing, I'm just trying to understand. </div></div></div>
</blockquote><div><br></div><div>SS3 is about SCM, not publishing. If you are just talking about simply publishing a software application for safe consumption, SAR files contain everything an application needs in one single file, which can be installed into base Squeak straight from the file-manager. The file represents one specific version of the app, so once you test that it works in a particular Squeak release, then you can feel comfortable that it will _always_ work, forever, guaranteed.</div>
<div><br></div><div>SqueakMap is just a catalog of Smalltalk SAR and .st script files, so you can do absolutely anything like check SS3 to see if there are updated MC packages / configs for the app and load them, for example. You could even look for updated resources from another place like Git or SqueakMap. You would want to be sure to have proper error-handling in your install script, though, in case the user doesn't have a network connection. Plus, the danger of doing this is that it is no longer _fixed_ so a problem might develop someday. That's why, for publishing an app with resources, I prefer to just pump out a new SAR file (and why I use a streamlined the SARBuilder, so its easy).</div>
<div><br></div><div>If you want to set up a complex development project where multiple remote developers are able to work on the code AND resources on an on-going and incremental basis, then the Metacello / Git combination would be the most powerful and sophisticated solution for that. For _only_ publishing, it's probably overkill, and nothing as safe as a fixed SAR file, but definitely powerful for development.</div>
<div><br></div><div>HTH,</div><div> Chris</div><div><br></div><div>PS -- I made a SARBuilder with a Maui-based UI that allows one to drag-n-drop resources straight in, and one-click to create a valid SAR.</div></div></div>
</div>