Erlang Runtime and packaging system

[Mickael Remond]

Hello,

As promised, we have published several new tools for packaging and
distributing Erlang applications.
Erlrt is a proof of concept, which does not yet handle dependancies and
versioning. This however demonstrate a simple way to install and manage
Erlang/OTP distribution.

The distribution site is located on: http://erlrt.process-one.net/

After having deployed an erlrt base for your system (archive is 1.5Mb),
you can decide which OTP library you would like to install.

Here is an example Erlrt session:

To start Erlang, go to the directory where archives have been unpacked.

$ cd erlrt
$ ./start.sh

It is possible to upgrade your Erlang installation using the command
prompt. 

    * list available packages

      > erlrt:available().

    * list installed packages

      > erlrt:installed().

    * install a package

      > erlrt:install("mnesia").

    * uninstall a package

      > erlrt:uninstall("mnesia").


Note that no build step are needed on the client machine (unlike
erlmerge). The build is made and maintained for the central repository
of code.

The applications build and packaged in REPOS (Yaws, ejabberd, Wings3d,
etc.) will be added to the Erlrt repository. No need to create specific
packaging for each platform.


Please note that for now, the Windows archive is not complete and it will not work.  This
will be fixed in the next days.


We have also updated the following software:

- New Erlang REPOS release: 1.4 beta 2 (Now based on R10B-9 for Linux,
Windows and MacOSX). Erlang REPOS is the basis for the central archive
repository.
See: http://support.process-one.net/doc/display/CONTRIBS/Erlang+REPOS

- Erlang R10B-8 for Zaurus archive has been uploaded to:
http://www.erlang-projects.org/Public/rpmdeb/erlang_for_zaurus/view

Comments and suggestions are very welcome.

-- 
Mickaël Rémond
 http://www.process-one.net/