[Debian-med-packaging] [covid-19] Help for ocaml package needed

[Shayan Doust]

Hello Andreas,

> I assume the mcl development is really stalled.  But I'd love to see a
> discussion between upstream and the maintainer of the 12-068 fork
> whether they could settle with a common code base which also includes
> the OCaml support.  May be the first step could be to open an issue
> at [1] and ask for updating the code base?

I will open an issue with [1] and see if I can suggest and co-ordinate
for a common code base, that of the latest mcl release that's been packaged.

> Thanks a lot for your investigation.

No problem :)

Kind regards,
Shayan Doust

On 29/05/2020 11:08, Andreas Tille wrote:
> Hi Shayan,
> 
> On Thu, May 28, 2020 at 09:04:56PM +0100, Shayan Doust wrote:
>> I had a look at the currently packaged mcl and the mcl clone (the one
>> with the bindings on github).
>>
>> The mcl[1] clone seems to be a lot older than the debian packaged;
>> looking at the _oasis file it seems like the version is 12-068~oasis4
>> compared to the packaged one which is 1:14-137. This means that the mcl
>> clone would actually be in sync and would be built on top of presumably
>> this debian mcl state[2] which is 8 years old. I'm worried about any
>> incompatibilities should the code base or the pristine tarball now
>> reflect the mcl clone instead.
> 
> I confirm that
> 
>    https://github.com/fhcrc/mcl/blob/master/VERSION
> 
> says "12-068" which is actually the 8 years old state.  In Debian we
> upgraded to version "14-137".  I wonder whether the author of the clone
> could try to re-check the code base?
>  
>> Any suggestions as to how I can go forward and incorporate this
>> OCaml-enhanced mcl, presumably not in a separate package due to the
>> duplication of code?
> 
> I assume the mcl development is really stalled.  But I'd love to see a
> discussion between upstream and the maintainer of the 12-068 fork
> whether they could settle with a common code base which also includes
> the OCaml support.  May be the first step could be to open an issue
> at [1] and ask for updating the code base?
>  
> Thanks a lot for your investigation.
> 
> Kind regards
> 
>       Andreas.
> 
>> [1]: https://github.com/fhcrc/mcl
>> [2]:
>> https://salsa.debian.org/med-team/mcl/-/commit/96b51bfc7549accf6306ad8000599ec16a174c30
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x6D7D441919D02395.asc
Type: application/pgp-keys
Size: 3374 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20200529/dd891036/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20200529/dd891036/attachment.sig>