On Fri, 27 Dec 2024 20:11:51 -0500
Thomas Frohwein wrote:
> On Thu, 26 Dec 2024 23:08:32 +0100
> Christopher Zimmermann wrote:
>
> > On Wed, Dec 25, 2024 at 05:29:26PM -0500, Thomas Frohwein wrote:
> > >On Thu, 19 Dec 2024 21:52:08 +0100
> > >Christopher Zimmermann wrote:
> > >
> > >> On
On Thu, 26 Dec 2024 23:08:32 +0100
Christopher Zimmermann wrote:
> On Wed, Dec 25, 2024 at 05:29:26PM -0500, Thomas Frohwein wrote:
> >On Thu, 19 Dec 2024 21:52:08 +0100
> >Christopher Zimmermann wrote:
> >
> >> On Thu, Dec 19, 2024 at 02:05:55PM -0500, Thomas Frohwein wrote:
> >> >chrisz@,
On Wed, Dec 25, 2024 at 05:29:26PM -0500, Thomas Frohwein wrote:
On Thu, 19 Dec 2024 21:52:08 +0100
Christopher Zimmermann 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 buil
On Thu, 19 Dec 2024 21:52:08 +0100
Christopher Zimmermann 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 like the general approach, because it avoids porti
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 like the general approach, because it avoids porting and maintaining
the dependencies.
I would prefer the opamroot-helper tar
Hi,
When we last had lang/haxe in ports, it was broken because of fetching
online OPAM packages during the build until we removed it. I wanted to
take a shot at resurrecting it. This is the latest release 4.3.6 and
the OCaml dependencies are now in a tarball of a locally created OPAM
root director
