this is cool Igor. can I get your scripts? (I'm working on a set to build the vms for mac, and your scripts would be helpful)
I think we need to move the vm making stuff into a more formal and repeatable process... so I think we need to bring the vmmaker into a ConfigurationOfVMMaker... if we can achieve that, we can automatize the building in a reliable way. So... if there are things inside cs's and other formats, we first need to package them into monticello files (that's why I packaged ClipboardExtended into VMMaker - my first contribution to vm :) ) that's my 2c. Cheers, Esteban El 18/12/2010, a las 7:31a.m., Mariano Martinez Peck escribió: > > > On Fri, Dec 17, 2010 at 11:13 PM, Igor Stasenko <[email protected]> wrote: > On 17 December 2010 22:37, Mariano Martinez Peck <[email protected]> > wrote: > > > > > > On Fri, Dec 17, 2010 at 9:17 PM, Igor Stasenko <[email protected]> wrote: > >> > >> In our nearest plans is make an automated (Hudson based) build setup > >> for Cog and Squeak VMs. > >> > >> > > > > this is cool igor!!! > > > >> > >> a) image version (or its URL(s) for download) > >> b) script for loading VMMaker (of concrete version) > > > > but how can you set a concrete version if the buid is automatic ? how do you > > know which version of VMMaker and ALL its dependencies? > > we will collect necessary info bit by bit. > Obviously, this knowledge is already sits over there, in image, > otherwise how else > we manage to build VMs till those days? > I just want to automate it, which will leave less space for human mistake. > > > are you going to use ConfigurationOfVMMaker ? if true, how is going to > > maintain it? > > > > i am not quite sure if metacello will be capable to keep all this info. > Some things may require using changesets or other kind of > non-packageable messy code. > We will see. Things are scary from distance :) > In any case i don't think that a config, which fully describing a > conglomerate used to generate VM sources and plugins > is any bit worse than image which contains same info. > Except that you can't diff two smalltalk images to see what difference > between them. > > > Igor, what I wanted to express (maybe I did it wrong), is that we need to > first solve a previous problem with the VM. > I think we first need to be able to TRACE! And for TRACE I mean, that for a > specific VM state, I can trace: > - which METACELLO version to use in order to generate sources. And with this > metacello version, we can guess ALL the versions of all requiered packages > - which SVN version > > If the idea is to always load all the latest code, then you can just load the > baseline of ConfigurationOfVMMaker and that's all. With svn is even easier. > > cheers > > mariano > > -- > Best regards, > Igor Stasenko AKA sig. > >
