Re: Help porting google mtail

On Mon, Dec 1, 2025 at 2:29 PM Abel Abraham Camarillo Ojeda <acamari@verlet.org> wrote:

On Mon, Dec 1, 2025 at 6:11 AM Stuart Henderson <stu@spacehopper.org> wrote:

On 2025/11/30 17:09, Abel Abraham Camarillo Ojeda wrote:
> 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

AFAIK: pkg.go.dev isn't something that you upload to, this and
https://proxy.golang.org/ (which is where ports normally fetches
go modules from) update things automatically when they're published.

Not sure what they would need to do to fix this, but I note that the
build instructions at https://github.com/google/mtail#building-from-source
don't work with current go versions either.

I don't think a fork is a good idea.

The port I sent has instructions in modules.inc comments about how to
regenerate by hand, and since there have been no real changes upstream
since Aug 2024 it doesn't seem hugely likely to need much time spending
on it unless something changes in the go compiler to break old stuff.
So I think I would be ok if someone wanted to import it. (tar
reattached)

I just reviewed the instructions, they seem doable by me. And, as you say,
this port doesn't update that often.

Can anyone import? 

Thanks 

Hi, as of march 3 I've tested this again and it works, can anyone import?

tgz reattached

Thanks