Re: go.port.mk: expose _GOARCH

2025-02-06 Thread Antoine Jacoutot
On Thu, Feb 06, 2025 at 11:44:15PM +, Stuart Henderson wrote: > ok OK as well. > > On 2025/02/06 23:37, Lucas Gabriel Vuotto wrote: > > On Wed, Feb 05, 2025 at 11:18:08PM +, Stuart Henderson wrote: > > > On 2025/02/05 21:50, Lucas Gabriel Vuotto wrote: > > > > Hi ports, > > > > > > > >

Re: go.port.mk: expose _GOARCH

2025-02-06 Thread Lucas Gabriel Vuotto
On Wed, Feb 05, 2025 at 11:18:08PM +, Stuart Henderson wrote: > On 2025/02/05 21:50, Lucas Gabriel Vuotto wrote: > > Hi ports, > > > > I've a WIP port for a Grafana plugin. Grafana expects the binaries in > > the plugin to be called whatever_plugin_openbsd_{amd64,arm64,...}. In > > my WIP port

Re: go.port.mk: expose _GOARCH

2025-02-06 Thread Stuart Henderson
ok On 2025/02/06 23:37, Lucas Gabriel Vuotto wrote: > On Wed, Feb 05, 2025 at 11:18:08PM +, Stuart Henderson wrote: > > On 2025/02/05 21:50, Lucas Gabriel Vuotto wrote: > > > Hi ports, > > > > > > I've a WIP port for a Grafana plugin. Grafana expects the binaries in > > > the plugin to be cal

Re: go.port.mk: expose _GOARCH

2025-02-05 Thread Stuart Henderson
On 2025/02/05 21:50, Lucas Gabriel Vuotto wrote: > Hi ports, > > I've a WIP port for a Grafana plugin. Grafana expects the binaries in > the plugin to be called whatever_plugin_openbsd_{amd64,arm64,...}. In > my WIP port, I solved that by using _GOARCH and adding it to SUBST_VARS, > but it might m