[MacPorts] #37641: couchdb-devel @1.3.0a1177555 Project moved to git

[MacPorts]

#37641: couchdb-devel @1.3.0a1177555 Project moved to git
------------------------------+--------------------------
  Reporter:  jeff-macports@…  |      Owner:  ryandesign@…
      Type:  update           |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.1.2
Resolution:                   |   Keywords:  haspatch
      Port:  couchdb-devel    |
------------------------------+--------------------------
Changes (by ryandesign@…):

 * owner:  macports-tickets@… => ryandesign@…
 * status:  new => assigned


Comment:

 Thanks, I'll have a more thorough look at this later. For now:

 You mentioned elsewhere wanting to maintain this port. Please feel free to
 include that in your patch: just change the maintainers line to your email
 address (in our obfuscated host:user format), optionally in addition to
 "openmaintainer" if you'd like to leave open the possibility of other
 committers making changes to the port. Hopefully you'll also want to
 maintain couchdb.

 pkgconfig is almost certainly a build dependency only, as probably are
 automake, autoconf, help2man, and perhaps libtool. That's something that
 still needs fixing in couchdb as well.

 Including the git branch in the version number is not a great idea since
 the git branch is essentially a random number, and so it won't always
 increase, and when it doesn't, we'll have to increase the epoch. Instead,
 I'd put the date corresponding to that git version into the version
 number. 1.4.0-20130101 or whatever.

 Thanks for bringing back some fixes from the couchdb port. We should
 strive to make couchdb and couchdb-devel as similar as possible. That
 includes the whitespace, though whitespace changes should be separate from
 functional changes. Ideally we'd have both ports using our standard
 whitespace style of 4 spaces (not tabs) per indent and things aligned into
 two neat columns.

 I see you removed the configure.ac patch. Does the current version of the
 configure script no longer call out to erlang to see if it has been
 compiled with ssl support? The reason we were using this patch in couchdb,
 and I just added it to couchdb-devel, is because apparently for some users
 that check failed, and the port already checks it so there's no benefit to
 checking it again in the configure script.

-- 
Ticket URL: <https://trac.macports.org/ticket/37641#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS