Some hosting providers are using FreeBSD, and having an extended release of Hugo available for FreeBSD amd64 would be great. Is there anything preventing that?
Is there anything preventing that?
A fix for this would make it ... simpler ... https://github.com/goreleaser/goreleaser/issues/705 -- @caarlos0 Christmas wish ...
But even with that; the extended build requires the C tool chain of the target platform installed. Which is why I kind of closed my eyes and said "let's just do this" when I introduced LibSASS and CGO into the build chain. It is still worth it (SASS is really useful), but it makes stuff harder. Docker makes all of this doable, but I'm waiting for a fix to the above issue before I add more "extended builds" to the mix.
@bep sorry this is taking too long.. new year's resolution is to do this haha
https://github.com/goreleaser/goreleaser/issues/705#issuecomment-450738025
I'd love for an extended FreeBSD release!
multiple archives is already there, but other parts are still missing...
@caarlos0 so something like this should work (I know the YAML is probably invalid ...)?
builds:
- binary: hugo
id: hugo_extended
- binary: hugo
id: hugo
archives:
- binaries: ['hugo']
name_template: 'hugo_{{.Version}}_{{.Os}}-{{.Arch}}'
- binaries: ['hugo_extended']
name_template: 'hugo_extended_{{.Version}}_{{.Os}}-{{.Arch}}'
yes, just instead of binaries its builds and you use the build.id
https://goreleaser.com/customization/#Archive
still need to finish the releasing parts (which archives to release where), as for now it releases all archives, ex: https://github.com/caarlos0/test/blob/master/.goreleaser.4.yml generates https://github.com/caarlos0/test/releases/tag/v5.6.0
Most helpful comment
@bep sorry this is taking too long.. new year's resolution is to do this haha
https://github.com/goreleaser/goreleaser/issues/705#issuecomment-450738025