[MacPorts] #38405: mochiweb fails to build for erlang upgraded to R16B

[MacPorts]

#38405: mochiweb fails to build for erlang upgraded to R16B
---------------------------+--------------------------------
  Reporter:  su1shi4fu3@…  |      Owner:  macports-tickets@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.1.3
Resolution:                |   Keywords:  haspatch
      Port:  mochiweb      |
---------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)
 * keywords:   => haspatch
 * port:   => mochiweb


Old description:

> After erlang got upgraded to R16B, mochiweb (v2.3.2) fails to build.
> Proposed solution: upgrade mochiweb to current head from github.
> (The latest tagged version of mochiweb, 2.4.2, also fails to build.)
> Patch below:
>
> --- a/Portfile  2012-09-21 22:23:57.000000000 +0200
> +++ b/Portfile  2013-03-17 00:11:20.000000000 +0100
> @@ -4,8 +4,8 @@
>  PortSystem      1.0
>  PortGroup       github 1.0
>
> -epoch           20111014
> -github.setup    mochi mochiweb 2.3.2 v
> +epoch           20130317
> +github.setup    mochi mochiweb 167f517416c3c48fa751af00188a42a4ca0f60e0
>  categories      erlang www
>  license         MIT
>  platforms       darwin
> @@ -19,8 +19,8 @@
>
>  depends_lib     port:erlang
>
> -checksums       rmd160  867b293145fd02fd138dbfa8d18b59a4579c9c00 \
> -                sha256
> 1376f867ccf178f27fa1a4d5a645a07fdf68861e0df3994a6e5a460bebc8adeb
> +checksums           rmd160  0dbdbbe29cef89e3a6ebb9ccc86c6ff1c36f2123 \
> +                    sha256
> aa72b4af4ce6e00a0c253752a1cd137a9eacd8070323336ad2303a350abe0a79
>
>  use_configure no
>  build.target-append edoc

New description:

 After erlang got upgraded to R16B, mochiweb (v2.3.2) fails to build.
 [[br]]
 Proposed solution: upgrade mochiweb to current head from github. [[br]]
 (The latest tagged version of mochiweb, 2.4.2, also fails to build.)

--

Comment:

 Using a git commitish as a user-facing version number is not optimal.

 Could we update to 2.4.2 instead, then patch it with whatever upstream
 changes are needed to make it work with erlang R16B? Or would those
 patches be very large?

-- 
Ticket URL: <https://trac.macports.org/ticket/38405#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X