Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
> we have a nice 1.x.x branch
Ah I missed that, nice!
> good question, do you want to ask this on the dev list?
Sure! Can you share the link to dev list please?
@dch reason I'm asking is because I'm trying to update the
[recipe](https://github.com/gmile/homebrew-core/blob/master/Formula/couchdb.rb)
on homebrew. It appears so that all homebrew users are stuck with 1.6.1 forever
(more than a year now). I do see an [old
commit](https://github.com/Homebrew/homebrew-core/commit/5cefb216b27d60772738458e9af411710676ccd4#diff-ccdcb18cac44281832236416670515d9R10)
from yours fixing support for erlang R18.0 and all I wanted is to expand
support to 19.0 as well.
I was hoping to update the couchdb recipe so that it'd unblock another
issue, related to upgrading Erlang recipe on homebrew to 19.0. There's an
evidence that updating erlang will break current couchdb 1.6.1 installation on
homebrew.
I saw a few options to resolve the issue with erlang recipe:
1. update the text of your patch directly (which I did in
https://github.com/Homebrew/homebrew-core/pull/2891) (it kind of feels wrong
and dishonest to update someone's code, given your credentials in that patch,
but if it's OK with you â maybe it's a way forward?),
2. do it _the proper way_â¢, and patch the 1.6.x branch first, and then
override the text of your patch with the text on my patch, including overriding
the credentials (this didn't work, see last edit to [this
comment](https://github.com/Homebrew/homebrew-core/pull/2891#issuecomment-231862749)),
3. do it even more proper way, tag a latest stable 1.x.x (1.6.x?) release,
and cleanup homebrew recipes accordingly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
