Could we get this and it's deps in portage? Thanks!
I added some hacked together ebuilds available in my overlay if it helps.
This is an enhancement, not a bug.
Is this still interesting? If so, attach the ebuilds and I will have a look at them.
It still is. I worked with upstream to clean up the build of rabbitmq-c as well (and got a proper tag out of them with no git externals).
(In reply to comment #4)
> It still is. I worked with upstream to clean up the build of rabbitmq-c as
> well (and got a proper tag out of them with no git externals).
Thanks. For USE=tools rabbitmq-c, could you add a metadata.xml describing what those tools are? See quse -D tools for examples of helpful descriptions.
Otherwise, for static-libs, I am not a fan of providing that USE flag unless it has a specific USE case to have libs built statically.
tools: builds cli tools to interact with brokers. including create/deleting queues, bindings, messages, etc.
examples: right now this builds them but we probably shouldn't. likely better to install the source/header files rather than the binaries
static-libs: no particular use-case at present. I don't mind seeing it go away if that's necessary.
Fixed in CVS.