[rabbitmq-discuss] Generating a Rabbitmq release

Matthew Sackman matthew at rabbitmq.com
Fri Apr 13 13:14:53 BST 2012

On Fri, Apr 13, 2012 at 01:55:26PM +0200, Alvaro Videla wrote:
> In my case I've been using Erlang for a few years already so I like to
> build it from source and so on, but some people don't. Actually some people
> just want to evaluate RabbitMQ and see if it's the right solution for them.
> If I can't get RabbitMQ running because something doesn't compile or
> whatever the reason, but then I download MagickMQ and it works like a charm
> then I will just evaluate MagickMQ and discard RabbitMQ. It's sad but it's
> how it works most of the time.

Indeed, and any sane package manager should do that for you. In fact
ideally, you shouldn't be downloading anything from our website - you
should just use your platform's native package manager and it should
install as you wish something that's appropriate for your particular
platform. The fact that that doesn't work for many people is somewhat

> I agree with you Matthew that you should learn how to compile Erlang,

Actually, I'm not saying that. If you just want to evaluate a bunch of
different message brokers, then no, I don't think you should take the
gentoo approach to everything. Even in a university course about
messaging, time is probably better spent not compiling Erlang. However,
in such a educational situation, I would say that learning your way
around toolchains is valuable. I would also hope that a course on
messaging didn't require every student to compile their own version of
Erlang and instead both Erlang and Rabbit would be provided on a
lab-wide system install.


More information about the rabbitmq-discuss mailing list