[erlang-questions] Erlang project dependency management/build tools

[Tim Watson]

On 21 January 2011 22:46, Eric Merritt <ericbmerritt@REDACTED> wrote:
> Tim,
>
>  Now whether or not faxien installs versions of the standard libraries
> is all up to you, where you install faxien and whats already there. If
> you install faxien on a clean system that doesn't have erlang it will
> pull down everything it needs. However, if you install it on a system
> that already has erlang installed, it wont pull down anything that is
> already there. faxien and sinan don't actually care where the
> libraries come from, as long as they are on the system.  If the
> libraries/versions that something requires are not there though, it
> will pull them down. Thats a bit different then it was at the
> beginning when faxien kind of managed its own little world, that is no
> longer the case however.
>

That's excellent news, I shall have a play once more then. I have to
admit that most of my open source projects are using rebar and it's
doing a fine job, but binary artefact repositories are the "norm" at
work and there's been a lot of suggestions about packaging Erlang/OTP
releases up and deploying them to our maven repositories. The reason
for this is that our automated deployment tooling (which is based on
capistrano) can easily grab hold of stuff that is in a know location
and pulling from source (especially external source repositories such
as github) would be frowned upon (despite the fact that for most open
source dependencies such as mochiweb, that's exactly where we've taken
the code from to begin with).

Anyway thanks for the update - I'll starting playing again.

Tim