Hi Kevin,
I have updated Navidrome in my personal tree. You can see the diff here
[1], however, as you can see, there are things that may not make sense
to you, such as MASTER_SITES and DISTFILES. This is how I prefer to
generate assets [2] (so I don't use the Makefile to generate the assets
either, which is why I've removed those parts), but you can change it
according to your preferences.
As you can see, GO_MODULE takes on most of the responsibility, which
greatly simplifies porting. You only need to be aware of the go.mod
file. Occasionally, you may encounter a project with an outdated go.mod
file when proxy.golang.org is used. In such cases, you will need to
retrieve it from the most up-to-date location, such as the upstream
repository. See also net/dataplaneapi for an example.
Just one last note: BROKEN_arm64 seems to be a typo, so I renamed it to
BROKEN_aarch64 and portclippy no longer complains. However, reading the
reason, perhaps generating the assets outside the ports framework on a
compatible arch could help. This might make sense if the assets are just
static files.
[1] https://people.freebsd.org/~dtxdf/patches/navidrome-0.58.0.diff
[2]
https://github.com/DtxdF/port-assets-makejails/blob/main/navidrome/Makejail#L13
