Index | Thread | Search

From:
Abel Abraham Camarillo Ojeda <acamari@verlet.org>
Subject:
Re: Help porting google mtail
To:
ports <ports@openbsd.org>, Stuart Henderson <stu@spacehopper.org>
Date:
Sun, 30 Nov 2025 17:09:43 -0600

Download raw body.

Thread
Hi Stuart,

I'm looking into this again,

Should I sent a email to mtail guys so they update their packages in
pkg.go.dev?
or maybe I can fork and upload it to pkg.go.dev with another name?
mtail-openbsd ?
maybe we can incorporate your port as-is and we regenerate somehow the
MODGO sections at update time?

I'd like to understand a path to get this incorporated into openbsd ports

Thanks

On Thu, Jul 17, 2025 at 7:36 AM Stuart Henderson <stu@spacehopper.org>
wrote:

> On 2025/07/17 05:04, Abel Abraham Camarillo Ojeda wrote:
> > Hi to all,
> >
> > I'm trying to port google mtail but I don't understand how go (and go
> ports work),
>
> > MODGO_VERSION = v3.0.0-rc9+incompatible # generated by make
> modgo-gen-modules
>
> This is the newest on
> https://pkg.go.dev/github.com/google/mtail?tab=versions
> but looking at https://github.com/google/mtail it isn't the latest.
>
> The usual "portgen go" and go.port.mk modules mechanisms can't fetch a
> current version and they break down with the +incompatible tag.
>
> Writing a port for this can be done but it's a bit of a bodge. Port
> attached with comments for the hairy bits. Updating will require
> constructing new MODGO_MODULES and MODGO_MODFILES sections by hand.
>
>