From: Christopher Zimmermann <chrisz@openbsd.org>
Subject: Re: resurrect lang/haxe with pre-packaged opam root
To: Thomas Frohwein <tfrohwein@fastmail.com>
Cc: ports@openbsd.org
Date: Thu, 26 Dec 2024 23:08:32 +0100

On Wed, Dec 25, 2024 at 05:29:26PM -0500, Thomas Frohwein wrote:
>On Thu, 19 Dec 2024 21:52:08 +0100
>Christopher Zimmermann <chrisz@openbsd.org> wrote:
>
>> On Thu, Dec 19, 2024 at 02:05:55PM -0500, Thomas Frohwein wrote:
>> >chrisz@, I would appreciate a look at this approach to handling OPAM
>> >dependencies during the build.
>>
>> I would prefer the opamroot-helper target to be reproducible by
>> fixing it to a defined commit on opam-repository. This could be
>> accomlished by downloading a specific snapshot of opam-repository and
>> pointing opam init to this snapshot.
>
>Thanks for your response. Not sure if I understand your response
>correctly - the opamroot-helper is meant to create the download of
>the dependencies from OPAM (at least get started) to then build the
>tarball to be provided at SITES.opamroot when updating the port. This
>is by necessity a fixed distfile for the ports build.

I'd do versioning of the haxe-opamroot distfile and opam-init like this:

COMMIT.opamroot =	a66a58b
SITES.opamroot =	https://thfr.info/distfiles/
DISTFILES.opamroot =	haxe-opamroot-${COMMIT.opamroot}.tar.bz2

[…]

     env OPAMROOT=/tmp/opamroot opam init --no-setup \
		"https://github.com/ocaml/opam-repository.git#${COMMIT.opamroot}"

I'm building right now on amd64. Have you tested any non-native archs ?

Christopher