Gearmand port

[andy@…]

Attached is a Portfile (my first) for gearmand. Wasn't sure if it was correct to break out libgearman, since they are distributed together upstream.

[andy@…]

gearmand Portfile

[andy@…]

Updated variants, and added a libdrizzle port:  http://github.com/andyfowler/my-macports/tree/master/devel/

[ryandesign@…]

Sorry, I did not see this ticket before committing Rodney Rehm's gearmand port in #24158. Please file new tickets for any changes to that port you'd like to see made. You may want to discuss with Rodney being co-maintainers of this port.

[rodney.rehm@…]

I'm not eager to maintain anything, if nobody expects me to. I just filed my Portfile so I might eventually throw it out of my local repository.

If I need to check for gearmand updates and update the Portfile accordingly in the future, please tell me now. I'll then setup feeds and stuff to monitor changes to gearmand.

[ryandesign@…]

Rodney, thank you for submitting your Portfile. The Portfile you submitted lists you as the maintainer, which means we do expect you to respond to tickets, keep the Portfile updated with the latest version of the software, and in general be responsible for this software in MacPorts. If you'd rather not maintain the port, let use know and we'll change the maintainers line. Maybe Andy would like to maintain it.

MacPorts includes a feature called livecheck to help you determine when a new version of the software is available. You can type "sudo port livecheck gearmand" to try it. As you see, the livecheck for gearmand is not working correctly and needs to be fixed, perhaps by incorporating the livecheck definitions Andy has in his version of the gearmand port in this ticket.

[rodney.rehm@…]

Ok, then I guess I'll have to read that macports documentation some time... Would you like to point me to the docs explaining how to actually maintain the Portfiles?

I'm currently merging Andy's Port into mine. (actually testing the installation of each variant right now) I'll have a look into the livecheck feature afterwards. Patch will be in soon.

[andy@…]

Feel free to holler if I can help. The libdrizzle variant requires the libdrizzle port (also in my Github), but is probably a pretty common need, since it provides MySQL support.

[ryandesign@…]

Replying to rodney.rehm@…:

Would you like to point me to the docs explaining how to actually maintain the Portfiles?

Other than  the Guide, generally, I'm not sure what to point you to. To request updates to ports, you file a ticket here in the issue tracker and add a unified diff for your requested changes.

Replying to andy@…:

The libdrizzle variant requires the libdrizzle port (also in my Github)

I don't see this port in our tree, nor a ticket requesting the port be added. Could you file a ticket for the request to add the libdrizzle port, as per usual?

[andy@…]

libdrizzle submitted as #24172

[rodney.rehm@…]

The requested diff can be found at #24171

I introduced Andy as maintainer, added Andy's livecheck, added the Port to some other categories (derived from memcached), and of course included Andy's dependencies and variants.

I installed and tested the variants (except for postgres and drizzle).