w3: rotd on the web & mcorba release.
Tyson Dowd
trd at cs.mu.OZ.AU
Wed Sep 23 15:04:05 AEST 1998
Hi,
These two changes will be committed separately.
DJ should look at them.
===================================================================
Estimated hours taken: 1
download/include/rotd.inc:
Make the releases of the day downloadable from the web and the
ftp site.
Re-arrange the text to make the downloads easy to see, and
put the waffle further down.
include/mcorba.inc:
news/mcorba_newsdb.inc:
Release MCORBA 0.1.
Make it downloadable from the web and the ftp site.
Index: download/include/rotd.inc
===================================================================
RCS file: /home/mercury1/repository/w3/download/include/rotd.inc,v
retrieving revision 1.2
diff -u -r1.2 rotd.inc
--- rotd.inc 1998/09/21 06:46:12 1.2
+++ rotd.inc 1998/09/23 04:58:11
@@ -11,25 +11,48 @@
snapshot of the development system. This is called a "release of the
day (ROTD)" and is given a version number "rotd-YYYY-MM-DD" according to
the date it was built. When the compiler passes all its tests, a ROTD
-is put into the beta-releases directory of the
-<A HREF="ftp://turiel.cs.mu.OZ.AU/pub/mercury/beta-releases/">
-Mercury ftp site</A>.
-The Mercury compiler is written in Mercury, and compiles Mercury into
-C code. These releases contain the Mercury code and the generated C
-code for the compiler. You need a C compiler (such as gcc) to build
-the compiler and runtime system. Once built, the Mercury compiler is
-capable of generating its own C code (the process of getting a compiler
-to compile itself is called <em>bootstrapping</em>, because it is like
-the compiler lifting itself up by its own boot straps).
+is put into the beta-releases directory.
<p>
+<B>Download releases of the day:</b>
+<ul>
+<li> <A HREF="<? echo $root; ?>/download/files/beta-releases/">
+Mercury web site</A><br>
+<li> <A HREF="ftp://turiel.cs.mu.OZ.AU/pub/mercury/beta-releases/">
+Mercury ftp site</A>
+</ul>
+<H3> Unstable ROTDS </H3>
+
For some people, the cutting edge is not enough, and they want the
bleeding edge. To help these developers, we have an <em>unstable</em>
release of the day. This is just like a ROTD, but may not have passed
all its tests. It is marked with a version number
-"rotd-YYYY-MM-DD-unstable", and is also available on the
-<A HREF="ftp://turiel.cs.mu.OZ.AU/pub/mercury/beta-releases/">
-Mercury ftp site</A>.
+"rotd-YYYY-MM-DD-unstable".
+<p>
+<B>Download unstable releases of the day:</b>
+<ul>
+<li> <A HREF="<? echo $root; ?>/download/files/beta-releases/">
+Mercury web site</A><br>
+<li> <A HREF="ftp://turiel.cs.mu.OZ.AU/pub/mercury/beta-releases/">
+Mercury ftp site</A>
+</ul>
+
+<H3> Contents of the ROTDS </H3>
+
+The Mercury compiler is written in Mercury, and compiles Mercury into C
+code. These releases contain the Mercury code and the generated C code
+for the compiler. You need a C compiler (such as gcc) to build the
+compiler and runtime system. Once built, the Mercury compiler is
+capable of generating its own C code (the process of getting a compiler
+to compile itself is called <em>bootstrapping</em>, because it is like
+the compiler lifting itself up by its own boot straps).
+<p>
+Numbered releases often have binary packages created, where even the
+C code has been pre-compiled, and you simply need to install the
+libraries and executables.
+If we have enough processing power, we may someday do the same for
+releases of the day, but at the moment you need to do the final step
+of compilation yourself.
<p>
Please treat ROTDs with caution -- although they are often very
useful and reasonably stable, they are not widely tested, and
cvs server: Diffing download/patches
cvs server: Diffing images
cvs server: Diffing include
Index: include/mcorba.inc
===================================================================
RCS file: /home/mercury1/repository/w3/include/mcorba.inc,v
retrieving revision 1.3
diff -u -r1.3 mcorba.inc
--- mcorba.inc 1998/09/21 08:49:03 1.3
+++ mcorba.inc 1998/09/23 04:58:12
@@ -13,13 +13,22 @@
<h3> Download MCORBA </h3>
-MCORBA is very much a work-in-progress, however we expect to have
+MCORBA is very much a work-in-progress, however we expect to soon have
enough written so that you can start using it to develop applications.
+For the moment the most important thing missing from the binding is
+some of the generated C++ code. You presently use the translator to
+see how IDL is transformed into Mercury.
+<P>
+<B>Download MCORBA:</B>
+<ul>
+<li> <A HREF="<? echo $root; ?>/download/files/mcorba/">
+Mercury web site</A><br>
+<li> <A HREF="ftp://turiel.cs.mu.OZ.AU/pub/mercury/mcorba/">
+Mercury ftp site</A>
+</ul>
-We are still cleaning up the MCORBA code to prepare for distribution.
-We expect to make a preliminary release very soon.
-MCORBA will be distributed under the GPL for the translator,
-and LGPL for the runtime library.
+MCORBA is distributed under the GNU GPL for the translator,
+and GNU LGPL for the runtime library.
<p>
You will need a copy of omniORB2, which you can freely download
from the <a href="http://www.orl.co.uk/omniORB/omniORB.html">
Index: news/mcorba_newsdb.inc
===================================================================
RCS file: /home/mercury1/repository/w3/news/mcorba_newsdb.inc,v
retrieving revision 1.2
diff -u -r1.2 mcorba_newsdb.inc
--- mcorba_newsdb.inc 1998/09/22 14:44:14 1.2
+++ mcorba_newsdb.inc 1998/09/23 04:58:13
@@ -16,6 +16,15 @@
$mcorba_newsdb = array(
+"23 Sep 1998" => array("MCORBA 0.1 available for download.",
+
+"The first release of MCORBA has been placed on the web site for
+download. It is not yet complete, but enough is there that you
+can see what transformations are done. The most important thing
+that is missing at the moment is the generation of some of the
+C++ code."
+),
+
"21 Sep 1998" => array("MCORBA web page added.",
"We've just added this page to the Mercury web pages."
--
Those who would give up essential liberty to purchase a little temporary
safety deserve neither liberty nor safety. - Benjamin Franklin
Tyson Dowd <tyson at tyse.net> http://tyse.net
More information about the developers
mailing list