<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6000.16809" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px">
<DIV>I agree about needing a new release.</DIV>
<DIV> </DIV>
<DIV>I suppose there is some value in maintaining a MINimal size binary distribution, but I think it would also nice to also provide a FULL distribution with everything pre-built. (Of course, this will eat up more space on elego machines.)</DIV>
<DIV> </DIV>
<DIV>I have ready access to Windows XP (32-bit and 64-bit) and Vista platforms. I would be glad to build and supply the distros for these platforms.</DIV>
<DIV> </DIV>
<DIV>Suggest we agree upon a plan and a timeframe.</DIV>
<DIV>a. make a tag or something in CVS that marks what will comprise the official sources for the release</DIV>
<DIV>b. agree upon distribution format (platform naming conventions, compressed archive format for MIN and FULL variants)</DIV>
<DIV>c. get a list of who is going to supply distros for which platforms</DIV>
<DIV>d. establish procedure for how the distros will be uploaded to elego</DIV>
<DIV>e. set a date for contributors to have the distros uploaded</DIV>
<DIV>f. have someone put together the web page showing links to all the distros along with updated installation instructions</DIV>
<DIV> </DIV>
<DIV>One sticky issue in the past has been target location. If we unpack a distro and put it in a different place in the filesystem tree, we don't want it to break. I know that cminstall attempted to adjust the cm3.cfg file to deal with location differences. Do we need/want to build an installer program or script to deal with this issue, perhaps even adjusting cminstall will suffice? Or, do we give a set of instructions on which file(s) to edit when moving the install location?</DIV>
<DIV> </DIV>
<DIV>For Windows, I don't mind building an installer. Perhaps the installer could let you choose whether to install the MIN or the FULL version.</DIV>
<DIV> </DIV>
<DIV>Also, I think the Tinderbox has been great, but perhaps it can be improved. I know I would like to see testing for Windows platforms added. I have an XP computer I can pretty much dedicate to this task. The problem is that I tried with Olaf's help to get it working, but there were too many dependencies on unix-type shell/script environment, and trying to force fit into cygwin didn't work well for the native Win32 implementation. Thoughts?</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy<BR><BR>>>> Mika Nystrom <mika@async.caltech.edu> 4/1/2009 6:25 PM >>><BR><BR>Actually I think that the thing that has caused me the most problems<BR>in the past is that the -min and the -src-all get out of sync, since<BR>the binary bootstrapping dists are often not distributed (for size<BR>reasons?) with full source archives from exactly the same date. So<BR>when you try to build src-all with the binary bootstrap, something<BR>goes wrong. It's the whole... ok I need a binary install (since<BR>it's a real compiler), but now I have to bootstrap everything. And<BR>then the bootstrap turns out not to be 100% compatible with the<BR>compiler sources, libraries, some little detail in m3tk, ...<BR><BR>Another way of saying this is "Isn't CM3 way overdue for a 'release'?"<BR><BR> Mika<BR></DIV></BODY></HTML>