Test VMMaker branch for 38b4 on SVN server

David T. Lewis lewis at mail.msen.com
Thu Nov 17 03:00:35 UTC 2005

On Wed, Nov 16, 2005 at 04:58:17PM -0800, John M McIntosh wrote:
> That has changed to
> http://squeakvm.org/svn/squeak/
> which is where the SVN tree has been moved to. The squeak.hpl.hp.com  
> SVN tree was frozen a few weeks back and moved.

That's news to me, glad you mentioned it.

> We're expecting HP at some point will wake up and drop that server,  
> but perhaps not until the end of the year.  mmm ping....
> mmm year end is early this  year, guess the IT dept at HP is somewhat  
> alert.

IT departments tend to be diligent and quite extraordinarily effective
in pursuit of objectives related to making things not work.

> On 16-Nov-05, at 4:49 PM, Brad Fuller wrote:
> >
> > How do others create a working environment for external plugin dev?

In general, if you just want to write a plugin, the versions of
VMMaker and Squeak image are not critical. This makes good sense,
since you would most likely want your plugin to work properly on
a range of Squeak images and VMs without modification. This also
means that just about any working Squeak with VMMaker will do just
fine as a development environment.

For myself, I am usually using a Linux platform, so I just grab
whatever source tarball is on Ian's web site, load up whatever
VMMaker might happen to be on Squeak Map, and carry on.

If you are doing something that really requires the latest and
greatest sources such a making sure your plugin is 64-bit clean,
then you will want to get the latest SVN sources and the latest
VMMaker. But this can be a lot of aggrivation at the moment, so I
would suggest starting with something old and stable to get under
way. Don't worry too much about the 64-bit cleanup, it turns
that it's quite straightforward to do later on.


More information about the Vm-dev mailing list