[rabbitmq-discuss] Generating a Rabbitmq release

[Alvaro Videla]

Hi Emile,

I know you can do that. What I want to do is to distribute the Erlang VM,
as mentioned in my first email when I said: "What I want to achieve is to
be able to generate a tar file with Erlang's erts and other dependencies as
explained here
http://www.erlang.org/doc/design_principles/release_structure.html#id75658".

What I'm thinking here is about usability. Some weeks ago I taught RabbitMQ
at an University and many students were complaining about the long
compiling times Erlang has. Also "what's the right Erlang distro for
Rabbit". Or "the Erlang distro for my ubuntu is too old". And so on.

Also if you monitor the #rabbitmq hashtag on twitter from time to time you
may find users complaining about "rabbitmq is hard to install" when the
actual problem is that they can't get Erlang running in the first place.

So I think producing a self container tar ball could be very helpful. As
RabbitMQ you can even choose against which Erlang version you want to
compile your code, which I think is another advantage.

Do you see where I want to go with this approach?

Regards,

Alvaro


On Fri, Apr 13, 2012 at 12:40 PM, Emile Joubert <emile at rabbitmq.com> wrote:

>
> Hi Alvaro,
>
> On 13/04/12 09:50, Alvaro Videla wrote:
> > Is there a way to generate a RabbitMQ release by using the make files
> > form the umbrella?
>
> You will find the release files (.boot, .script and .rel) in
> ${RABBITMQ_MNESIA_BASE}/${RABBITMQ_NODENAME}-plugins-expand
> after starting the broker.
>
> What the RabbitMQ Makefiles do produce is an Erlang application, with a
> rabbit.app file. You can start, stop and manage the rabbitmq application
> in the same way as any other Erlang application.
>
> > In that way we could distribute RabbitMQ without the need to install
> > Erlang, which I think will ease adoption a lot.
>
> The approach that ejabberd takes is to install a minimal version of
> Erlang together with their binaries. That is similar to Java
> applications that bundle and install a dedicated JVM. There are
> advantages and drawbacks to this approach. In either case you still need
> an Erlang VM, whether it is distributed with the service (like ejabberd)
> or installed independently (like RabbitMQ requires).
>
> -Emile
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120413/7f4622cf/attachment.htm>