It's not intentional, it just hasn't been implemented yet. Looks like nfpm does support different architectures but not different binaries for these architectures. If I understand it correctly that means we'd need to template the nfpm config file and run it once for every architecture, adding the previously built binaries for each arch.
Do you want to send a PR?
It's not intentional, it just hasn't been implemented yet. Looks like nfpm does support different architectures but not different binaries for these architectures. If I understand it correctly that means we'd need to template the nfpm config file and run it once for every architecture, adding the previously built binaries for each arch.
Do you want to send a PR?
I'm afraid the whole Go ecosystem, including its build tools, is rather unfamiliar to me. I'm still not quite clear which components are involved in building Vikunja and how they interact.
(Sorry for the closing/reopening. I pressed the wrong button.)
> Do you want to send a PR?
I'm afraid the whole Go ecosystem, including its build tools, is rather unfamiliar to me. I'm still not quite clear which components are involved in building Vikunja and how they interact.
(Sorry for the closing/reopening. I pressed the wrong button.)
The nfpm config docs show they expand environment variables, maybe that could be used to release packages from different binaries (talking about the ci)
Sure, that's fine!
The nfpm config docs show they expand environment variables, maybe that could be used to release packages from different binaries (talking about the ci)
https://nfpm.goreleaser.com/configuration/
I would like to install the backend on a Debian armhf server. Is it intentional that the Debian package is only available for amd64?
It's not intentional, it just hasn't been implemented yet. Looks like nfpm does support different architectures but not different binaries for these architectures. If I understand it correctly that means we'd need to template the nfpm config file and run it once for every architecture, adding the previously built binaries for each arch.
Do you want to send a PR?
I'm afraid the whole Go ecosystem, including its build tools, is rather unfamiliar to me. I'm still not quite clear which components are involved in building Vikunja and how they interact.
(Sorry for the closing/reopening. I pressed the wrong button.)
Sure, that's fine!
The nfpm config docs show they expand environment variables, maybe that could be used to release packages from different binaries (talking about the ci)
https://nfpm.goreleaser.com/configuration/