On Tue, 2 Apr 2019 11:50:32 +0200, Christopher Zimmermann
<chrisz@openbsd.org> wrote:
> On Tue, 2 Apr 2019 10:41:58 +0100
> Anil Madhavapeddy <anil@recoil.org> wrote:
>
> > I'm also working on a non-April fools joke, which is sufficient
> > metadata in dune to generate reliable openbsd ports. So in a few
> > months, we should be able to type in package names and have
> > reasonable Makefiles output for the ports (including WANTLIB etc).
> > Am doing it for Homebrew and a few other operating systems as well
> > to see if we can sidestep the port maintainer burden somewhat.
> > Unsure yet if it'll be suitable for usage in OpenBSD, but at a
> > minimum it'll generate sufficient scaffolding for a human ports
> > maintainer to tweak for upstreaming.
>
> That's an interesting idea, I also thought about, but was wondering
> whether to generate the port from OPAM metadata or create a package
> from opam builds. This would obviously not integrate with the ports
> infrastructure. But would it even need to?
You can look at sysutils/upt. It's not something specific for OpenBSD.
It works with "frontends" (language-specific packages systems, cpan pip
etc) and "backends" (OS-specific packages systems). There's already an
OpenBSD backend so you need to only add a ocaml frontend.
I used it for python ports and it does a lot of the grunt work.
cc (per his request) the author
Cheers,
Daniel
No comments:
Post a Comment