From: Stuart Henderson Subject: Re: Help porting google mtail To: Abel Abraham Camarillo Ojeda Cc: ports Date: Mon, 1 Dec 2025 12:11:13 +0000 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). > On Thu, Jul 17, 2025 at 7:36 AM Stuart Henderson 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. > >