On 23 March 2024 14:55:10 GMT+01:00, Oliver Bandel <oli...@first.in-berlin.de> wrote: >Quoting Marcell Meszaros <marcell.mesza...@runbox.eu> (snt: 2024-03-23 07:22 >+0100 CET) (rcv: 2024-03-23 07:22 +0100 CET): >> On 17 March 2024 14:30:01 GMT+01:00, not...@aur.archlinux.org wrote: >> >MarsSeed [1] filed a deletion request for ocamlnet [2]: >> > >> >Broken for close to 1 year due to not being compatible with repo's >> >ocaml 5, first published in May 2023. >> > >> >Upstream seems to be abandoned (developer only attends to their other >> >projects). >> > >> >There has been a work-in-progress, partially viable port to ocaml 5, >> >contributed to upstream in the form of a merge request 1.5 years ago, >> >but it has been abandoned and ignored since. [a] >> > >> >That unfinished patch does not make this buildable. Also, now the code >> >does not support the current gnutls, needed for https support in this >> >library. >> > >> >Downstream dependents have either moved on to other solutions, or got >> >discontinued 3+ years ago. (All AUR reverse dependencies have been >> >submitted for deletion.) >> > >> >I think it's best to delete this package. >> > >> >[a]: https://gitlab.com/gerdstolpmann/lib- >> >ocamlnet3/-/merge_requests/21 >> > >> >[1] https://aur.archlinux.org/account/MarsSeed/ >> >[2] https://aur.archlinux.org/pkgbase/ocamlnet/ >> >> >> The last package change is ill-conceived. The build stays broken. >> >> A package cannot depend on both 'ocaml' (v5) and 'ocaml4', as they conflict >> with each other. Still not useful to keep this library that is EOL for 3+ >> years. > >I asked the author of ocamlnet, if it was planned to update it for OCaml5. >The answer was yes. >So far there is no time plan for that, but next week I may habe more >information. >
It was asked from developer of ocamlnet more than one year ago (Fev 2023), and he didn't bother to answer. [a] Also there were work-in-progress were pull request commits submitted, but dev couldn't care less. And the submitting users admitted they are facing some difficulties and had hit a roadblock in making the patch work properly. [a]: https://gitlab.com/gerdstolpmann/lib-ocamlnet3/-/issues/27
