You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In many cases this is fine but if I want to toggle no_unique_dist_dir and then use the binary property to reimplement a different "unique" structure, the entirety of that path appears in the archive.
builds:
- id: turbomain: ./cmd/turbono_unique_dist_dir: truebinary: turbo-{{.Os}}-{{ if (eq .Arch "amd64") }}64{{ end }}{{ if not (eq .Arch "amd64") }}{{ if (eq .Arch "386") }}32{{ end }}{{ if not (eq .Arch "386") }}{{ .Arch }}{{ end }}{{ end }}{{ if not (eq .Ext ".exe") }}/bin{{ end }}/turboarchives:
- id: defaultwrap_in_directory: truefiles:
- LICENSE
- README.md
One attempted workaround which almost does what I want:
archives:
- id: defaultwrap_in_directory: truefiles:
- LICENSE
- README.md
- src: dist/turbo-{{.Os}}-{{ if (eq .Arch "amd64") }}64{{ end }}{{ if not (eq .Arch "amd64") }}{{ if (eq .Arch "386") }}32{{ end }}{{ if not (eq .Arch "386") }}{{ .Arch }}{{ end }}{{ end }}{{ if (eq .Os "windows") }}/turbo.exe{{ end }}{{ if not (eq .Os "windows") }}/bin/turbo{{ end }}dst: .strip_parent: true
This enables me to place the asset where I want it; but I am unable to prevent the addition of the binary at the full path:
Is your feature request related to a problem? Please describe.
I would like to be able to control the placement of the binary within the archive separately from placement within
dist
.Archive output:
In many cases this is fine but if I want to toggle
no_unique_dist_dir
and then use thebinary
property to reimplement a different "unique" structure, the entirety of that path appears in the archive.Archive output:
Describe the solution you'd like
I'd propose a new
binary
key inside of thearchive
object which enables me to specify the name relative to the root of the produced archive.(Aside: currently
Ext
isn't plumbed through toarchives
templates.)Archive output:
Describe alternatives you've considered
One attempted workaround which almost does what I want:
This enables me to place the asset where I want it; but I am unable to prevent the addition of the binary at the full path:
Archive output:
Search
Code of Conduct
Additional context
meta: true
in the archive immediately breaks because it is no longer per-build.The text was updated successfully, but these errors were encountered: