Re: Porting a new Golang app: go mod replace relative path

I have made some updates to the PR. Please advise if I should open a new PR to address the feedback. El mar, 23 de jul de 2024, 17:36, Zach Leslie escribió: > I'm on mobile, but #279042 was filed. > > El mar, 23 de jul de 2024, 17:35, Zach Leslie > escribió: > >> Excellent thank you. There ha

Re: Porting a new Golang app: go mod replace relative path

I'm on mobile, but #279042 was filed. El mar, 23 de jul de 2024, 17:35, Zach Leslie escribió: > Excellent thank you. There has been a new version and I'd like to update > soon. I'll pr and send an email next time. Btw, there is a bug for this > new port. > > El mar, 23 de jul de 2024, 05:34,

Re: Porting a new Golang app: go mod replace relative path

Excellent thank you. There has been a new version and I'd like to update soon. I'll pr and send an email next time. Btw, there is a bug for this new port. El mar, 23 de jul de 2024, 05:34, Matthias Fechner escribió: > Am 24.04.2024 um 18:26 schrieb Zach Leslie: > >> maybe by an additional man

Re: Porting a new Golang app: go mod replace relative path

Am 24.04.2024 um 18:26 schrieb Zach Leslie: maybe by an additional manually added distfile entry to place it in the expected directly (maybe in a prefetch rule or by just manually extending the DIST_FILES). Thank you for the pointers. I was able to get something working and have submitted the f

Re: Porting a new Golang app: go mod replace relative path

On 25/04/24 03:26, Zach Leslie wrote: maybe by an additional manually added distfile entry to place it in the expected directly (maybe in a prefetch rule or by just manually extending the DIST_FILES). Thank you for the pointers. I was able to get something working and have submitted the follow

Re: Porting a new Golang app: go mod replace relative path

> maybe by an additional manually added distfile entry to place it in the > expected directly (maybe in a prefetch rule or by just manually extending > the DIST_FILES). Thank you for the pointers. I was able to get something working and have submitted the following pull request for this new port.

Re: Porting a new Golang app: go mod replace relative path

Am 19.04.2024 um 19:44 schrieb Zach Leslie: ===> Fetching github.com/grafana/alloy dependencies go: github.com/grafana/alloy/syntax@v0.1.0 (replaced by ./syntax): reading syntax/go.mod: open /usr/ports/distfiles/go/sysutils_alloy/grafana-alloy-v1.0.0_GH0/syntax/go.mod: no such file or directory

Porting a new Golang app: go mod replace relative path

Good day, I've been trying to create a new port and running into an issue. Here is the port: https://github.com/zachfi/personal-ports/blob/main/sysutils/alloy/Makefile Here is the source of the issue: https://github.com/zachfi/personal-ports/blob/main/sysutils/alloy/Makefile When running `make