On Wed, Jun 19 2019, Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote:
> On Wed, Jun 19 2019, 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?
>
> ok jca@ to mark lang/ocaml-camlp4 as BROKEN with ocaml-4.08, which
> should be sufficient for now.

And just to make things clear: please don't mark it BROKEN before the
ocaml-4.08 update is committed.

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

Reply via email to