RabbitMQ (http://www.rabbitmq.com/) is a freely available AMQP-compliant message broker written in Erlang. This bug is intended to collect feedback and eventually develop an ebuild. Reproducible: Always Steps to Reproduce: 1. try "emerge rabbitmq" 2. no profit? I may get the ball rolling with an initial ebuild, but any and all feedback regarding fs layout, configuration/env variables, mnesia locations, dependencies (likely dev-lang/erlang) etc. is appreciated.
Has there been any further progress on this? I don't have much experience writing ebuilds, but may give it a go if nobody has already made a start.
(In reply to comment #1) > Has there been any further progress on this? /me hangs head in shame I have started with this in my overlay, but it does not install yet. I *do* intend to finish this (maybe by the end of the week), it's just that I get distracted! Much appreciate the offer, though. Btw I decided to go with the binary dist since there is no benefit to compiling, and the rabbit Makefile is rather homegrown which makes things more difficult than necessary. I'll definitely update this when something is ready for testing. And thanks for the interest, you're the first person outside of LShift/CohesiveFT to be interested in this. :)
(In reply to comment #2) Forgot to mention that one reason for the delay was the change in some filesystem locations between rabbit 1.3 and 1.4 (about which I knew beforehand). The generic defaults are now pretty good for Gentoo so that makes things easier.
Steven, as promised I got off my lazy bum and made it work. :) The first version installs cleanly into the erlang modules directory, but does not yet have any conf.d/init.d support so help is welcome. It can be found in my overlay at http://hoho.dyndns.org/hg/ in the net-misc categoryy. Feel free to clone and hack away if you feel adventurous, there are a few TODO items mentioned. If you are not familiar with hg let me know and I will attach stuff here.
Steven, did you get a a chance to play with Rabbit yet? Let me know if you need help or want to improve the ebuild somehow.
(In reply to comment #5) > Steven, did you get a a chance to play with Rabbit yet? Let me know if you need > help or want to improve the ebuild somehow. Yes thanks, it works fine as it is. It is possible it could benefit from ways to set things like the user it is run as, but will wait and see what is required as I use it.
(In reply to comment #6) > It is possible it could benefit from ways to set things like the user it is run > as, but will wait and see what is required as I use it. Glad to hear that it works for you. Please feel free to add user, config or anything else you find and send me patches or a repo URL to pull from. :) I guess proper conf.d or init.d scripts would be most important but as I am currently not using Rabbit at all I probably won't get to fix those things.
(In reply to comment #0) required =dev-python/simplejson-2.0.4 to build on my machine
rabbitmq-1.6.0 "final beta", whatever that means, has been released: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090617/c0781ab0/attachment.txt
I'm trying to install PygoWave http://code.google.com/p/pygowave-server/wiki/PyGoWaveServerInstallation which has rabbitmq & rabbit-stomp as requirements. Unfortunately, the current high watermark of the PygoWave code references a RabbitMQ 1.6. rabbit-stomp only has versions in mercurial of 5_1, 5_3, & 5_5. Gentoo only offers RabbitMQ of 5_4. I tried upper and lower releases of rabbit-stomp and still am having crashes on the rabbit-stomp code as modified by PygoWave. I do note that rabbit-stomp cautioned that its version should match the rabbitmq version. So I'm going to have to manually install a different version of the rabbit server to meet the lack of a rabbit-stomp 5_4 release. All this is to show that someone is using rabbit in Gentoo. (I wish I were knowledgeably enough in matters of Gentoo to help by submitting ebuilds for other versions.)
Created attachment 206794 [details] ebuild for rabbitmq-server-1.7.0 This is an updated ebuild for 1.7.0. The only relevant change is for the new activate/deactive-plugins commands (not sure if those should go into /usr/sbin or /usr/bin?) and the rabbitmq-env script, which has to be copied into both /usr/bin and /usr/sbin because otherwise it won't be found by the respective commands. Maybe a symlink from /usr/sbin to /usr/bin would be better, if it works - haven't checked.
Thanks, Holger, for the 1.7.0 ebuild. Is this something that I wait for to be taken up into Portage? Or is there a way to use it now? (I'm also trying my own hand an creating an ebuild in a portage overlay so I can install this without resorting to hand installations.)
(In reply to comment #13) Yes, if you have your own overlay as explained in the guides then you can just drop this into youroverlay/net-misc/rabbitmq-server/, run "ebuild <ebuild> manifest" and be able to emerge it.
Created attachment 208659 [details] ebuild for rabbitmq-server-1.7.0 Here's an update on Holger's ebuild : * fix the directory where erlang libs are installed so that erlang's "-include_lib()" statement works * fix the sed command for new scripts (finding where rabbitmq-env is located) * only copy rabbitmq-env in /usr/sbin, since we've now told the scripts where to find it I dont think that handling rabbitmq-env this way is very nice, but then again I blame upstream for comming up with such a scheme in the first place :p
I think it's time to close this (since an initial version in in portage) and continue discussion about an update to 1.7.0 in bug#290820. I'll attach the last ebuild there.
i've commited 1.8.0 to cvs
