Alexis/David,<div><br></div><div>I think the response from the group has been awesome. �Takeaways:</div><div><br></div><div>1. Everybody who is on a Mac likes Homebrew. �It should at least be referred to on the downloads page, and most likely, it should be the default installation recommendation for Mac users. �</div>
<div>2. David�should make appropriate tickets on the Homebrew site (individual ones, not one big one) for the naming conventions, etc... that you would like homebrew to use. �I'm sure they'll be evenhanded. �Note item #3 though when making the tickets.</div>
<div>3. Virtually all Mac users of rabbitmq are using it for development. �Production installations for the Mac users are running Linux (frequently Ubuntu).</div><div>4. The documentation needs a major overhaul - soon.</div>
<div>5. The codebase should be hosted on Github.com for easier interaction with the wider community.</div><div>6. "it's unlikely we are going to�repeat that effort for homebrew (unless macports dies or something)." -�Macports is dying - I hate to break it to people. �Agreed, it is way ahead of Homebrew in maturity, but MacPorts is too flawed to continue on. �The fundamental issue is that Mac is not a server OS, so the pace of iteration on the platform is much faster than on something like Debian/Ubuntu where it's been using the same package manager for years and will continue to be. �All the mature features of MacPorts are useless because nobody uses Mac as a server for anything but internal office functions and specialized rendering stuff. �The vanguard of Mac users has already moved to Homebrew even though it's only a few months old - that battle is over.</div>
<div><br></div><div>Thanks so much for all the support from everybody on these issues. �I'd love to continue using RabbitMQ and it's these types of rough edges that matter to alot of us.</div><div><br></div><div>Thanks,</div>
<div>Adam</div><div><br><div class="gmail_quote">On Thu, Sep 23, 2010 at 5:50 PM, Alexis Richardson <span dir="ltr"><<a href="mailto:alexis@rabbitmq.com">alexis@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Adam, everyone,<br>
<br>
What are your thoughts on this thread? �Is this helping?<br>
<br>
alexis<br>
<div><div></div><div class="h5"><br>
<br>
<br>
On Thu, Sep 23, 2010 at 1:22 PM, David Wragg <<a href="mailto:david@rabbitmq.com">david@rabbitmq.com</a>> wrote:<br>
> Adam Nelson <<a href="mailto:adam@varud.com">adam@varud.com</a>> writes:<br>
>> �* Please don't tell Mac users to use MacPorts:<br>
>> <a href="http://www.rabbitmq.com/macports.html" target="_blank">http://www.rabbitmq.com/macports.html</a> It's time to move them to HomeBrew at<br>
>> <a href="http://github.com/mxcl/homebrew" target="_blank">http://github.com/mxcl/homebrew</a><br>
><br>
> I'm not a frequent OS X user. �I do have some experience with macports,<br>
> but it's been mixed. �So I like to think I have a fairly objective view<br>
> on the macports vs. homebrew thing (that being, they are both vastly<br>
> inferior to current Linux package systems :-)<br>
><br>
> So with that said:<br>
><br>
> I think we'd be happy to endorse homebrew alongside or instead of<br>
> macports, *if* it achieves parity with the rabbitmq-server port, and the<br>
> rabbitmq-server packages on Linuxes. �That means:<br>
><br>
> - The formula should be called rabbitmq-server<br>
><br>
> - It should create and use a rabbitmq user/group, and include the<br>
> �wrapper scripts to support this.<br>
><br>
> - It should have some way to run as an automatically started daemon.<br>
><br>
> - It should include the man pages (on-line documentation is great, man<br>
> �pages are too, we have both, and we want the man pages to be provided<br>
> �with the packages).<br>
><br>
> - We need to have a way to distribute an update package when we make a<br>
> �new release, for users that are willing to bypass the central<br>
> �repository.<br>
><br>
> We've made all this work for macports; it's unlikely we are going to<br>
> repeat that effort for homebrew (unless macports dies or something).<br>
><br>
> But if someone in the community wants to work on getting the homebrew<br>
> formula into the same shape, that would be great. �We could work with<br>
> them to integrate it into our build/release process.<br>
><br>
> David<br>
><br>
> --<br>
> David Wragg<br>
> Staff Engineer, RabbitMQ<br>
> SpringSource, a division of VMware<br>
</div></div><div class="im">> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
</div>> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
><br>
</blockquote></div><br><br clear="all"><br>-- <br>Adam<br>
</div>