[M3devel] new cm3 release (was: Help finding CM3 compiler for Linux?)

[Daniel Alejandro Benavides D.]

Hey what a port of the tinderbox to Obliq, in that way, we could allow the system to test and report hosted on itself and get a hand from the M3 runtime capabilities, network objects and pretty staff (GUIs included, it could allow even to test directly from the Obliq interpreter without recompiling nothing, just using M3 runtime), however depending on M3 runtime I don't know is that is the idea, I think it makes sense since it's supposed to be a M3 system in the platform to be tested and reported. If the test failed there should be a lastok obliq script and runtime that worked so it can be in any case reported on the status web page.
With CM3-IDE we could also create a Link from the Initial web page to see the status locally and get or send reported status more easily integrated?

Oh, I would like to help but still I haven't checked the latest versions of the complete system, I still want to wait to have all server services running on Elego.de (thanks all there cvs is running) but we can think meanwhile on it.

Thanks in advance

--- El mié, 1/4/09, Randy Coleburn <rcoleburn at scires.com> escribió:
De: Randy Coleburn <rcoleburn at scires.com>
Asunto: [M3devel] new cm3 release (was: Help finding CM3 compiler for Linux?)
Para: m3devel at elegosoft.com
Fecha: miércoles, 1 abril, 2009 6:05


 
I agree about needing a new release.
 
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.)
 
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.
 
Suggest we agree upon a plan and a timeframe.
a.  make a tag or something in CVS that marks what will comprise the official sources for the release
b.  agree upon distribution format (platform naming conventions, compressed archive format for MIN and FULL variants)
c.  get a list of who is going to supply distros for which platforms
d.  establish procedure for how the distros will be uploaded to elego
e.  set a date for contributors to have the distros uploaded
f.  have someone put together the web page showing links to all the distros along with updated installation instructions
 
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?
 
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.
 
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?
 
Regards,
Randy

>>> Mika Nystrom <mika at async.caltech.edu> 4/1/2009 6:25 PM >>>

Actually I think that the thing that has caused me the most problems
in the past is that the -min and the -src-all get out of sync, since
the binary bootstrapping dists are often not distributed (for size
reasons?) with full source archives from exactly the same date.  So
when you try to build src-all with the binary bootstrap, something
goes wrong.  It's the whole... ok I need a binary install (since
it's a real compiler), but now I have to bootstrap everything.  And
then the bootstrap turns out not to be 100% compatible with the
compiler sources, libraries, some little detail in m3tk, ...

Another way of saying this is "Isn't CM3 way overdue for a 'release'?"

    Mika



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090401/3ea5b95f/attachment-0002.html>