[erlang-questions] Re: Library management in erlang.

[Christophe Romain]

look at CEAN
http://cean.process-one.net/

usage is described here
http://cean.process-one.net/doc/
you can search list install update....

The problem is that this has been done on spare time, it's quite
outdated now (R12B-4 based), and spare time is more than seldom.
I have R13B04 repository working with lots of code upgrade, but need
to update the official site and make automatic daily update running
on the site.

Both erlware and cean have pros/cons depending of what you need. Both
are really usable systems. Anyway, Erlang really lack of an "official"
and "standard" packaging centralized/mirrored solution.
That's what i tryed to do with CEAN. let's take an example on yaws packet:
http://cean.process-one.net/packages/index.yaws?action=detail&name=yaws
each package contains all needed metadata.

CEAN automatically get project sources and format it the OTP way so all
packages should be ready to use. It also try to automatically guess
status of packages (see http://cean.process-one.net/status/)
CEAN also does not depend on an erlang installation. you can just
download CEAN bootstrap (3Mb) and you have an erlang shell in 1 minute
without any root privilege.

We're talking about erlang packaging for more that 4 years, i'd really
like the community to have a concencus on what we need and how we
do/maintain it. spreading in many systems is not good, except if we have
gateways (i'm almost certain we could write script that exports cean's
package to erlware and import erlware contribution as cean package)
By the way, i really liked Joe's idea on elib, and i think it can be good
practice.

any thoughts ?