> On Jun 19, 2019, at 10:48 AM, Christopher Zimmermann <chr...@openbsd.org>
> wrote:
>
> On Tue, 18 Jun 2019 14:17:49 -0400
> ygrek <yg...@autistici.org> wrote:
>
>> On Mon, 17 Jun 2019 20:34:41 +0100
>> Anil Madhavapeddy <a...@recoil.org> wrote:
>>
>>> I think this approach is fine for this particular package, since
>>> upstream lags in recent times.
>>>
>>> The opam package for mldonkey is on ocaml<4.06, but I'm CCing the
>>> current maintainer Ygrek in case there is a 4.08 port in the
>>> offing.
>>
>> 4.08 support depends on camlp4 which is not yet available.
>> I am maintaining git repository at github.com/ygrek/mldonkey - it
>> builds fine with 4.07
>
>>>> Is this the way to go? OK to commit?
>>>> Is this port still in use?
>>
>> I don't think this is a good way forward if that package is used on
>> non-x86 archs, there were many bugs there in older ocaml versions.
>
>
> Ok. So mldonkey is the only port still using deprecated camlp4.
> I already adapted camlp5 to OCaml 4.08, because coq needs camlp5.
> But I'm reluctant to do the same for deprecated camlp4.
>
> * sthen@, krw@ already consented with removal of mldonkey
> * anil@ proposed to disable the port (and therefore camlp4, too)
> until camlp4 catches up.
>
> For the time being I would like to choose the second option and disable
> mldonkey and camlp4, but only enable them again on request.
> Then when no one complains and they have rotten long enough we can
> dispose of them.
>
> OK?
Perhaps just mark camlp4 as BROKEN (which will effectively disable mldonkey)
and then move on with the update of ocaml... ok daniel@ if you want to do that.
If the situation changes, it can be repaired in tree.
I would like to see ocaml 4.08 in the tree and don’t think these should hold
things back. Thanks for leading the charge!
>
>
> Christopher
>
>
>
> --
> http://gmerlin.de
> OpenPGP: http://gmerlin.de/christopher.pub
> CB07 DA40 B0B6 571D 35E2 0DEF 87E2 92A7 13E5 DEE1
