maintaining packages in macports vs. in a language package manager

Sergio Had vital.had at gmail.com
Mon Mar 11 07:51:23 UTC 2024


From my limited experience, most of OCaml ports are pretty trivial to write portfiles even by hand. (This does not apply to heavy and complex stuff like coq, of course.)

You just need to pick the right build system and use existing port examples.

But yes, automatic parsing would be helpful to have. (If anyone knows about the same for R packages, that would also be great.)


> On Mar 11, 2024, at 5:58 AM, Perry Metzger <perry at piermont.com> wrote:
> 
> On 3/9/24 13:26, Zero King wrote:
>> It seems that we are going with option 2 for ocaml ports now and many new ports
>> have being added. Are you aware of any tool like pypi2port that could help
>> speed up the process of packaging new ocaml ports for MacPorts?
> 
> So I'm not familiar with such a tool yet. However, opam files contain all the information MacPorts would want to build an ocaml package, and it should be very simple to parse them into Portfiles. The format of an opam file is pretty trivial. I never have had the time to do this, but it would be very welcome if someone did it.
> 
> Perry
> 



More information about the macports-dev mailing list