unexpected behavior in archive:files: section -- how to specify no additional files

[client9]

Prerequisites

• Are you running the latest version? HEAD
• Did you perform a search to see if this problem was already reported?

For more information, see the CONTRIBUTING guide.

Description

It's not clear how to specify no additional files to be included in the archive. Bug? Doc Bug? Feature?

Environment

$go version
go version go1.10 darwin/amd64

$ uname -a
Darwin nickg-macbook 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64

Steps to Reproduce

i wanted "classic goreleaser" behavior where the tar.gz contained just the binary. Currently, it tries to add license, readme and changelog info.

In the archive stanza, in the files section, I tried

• empty. That just used the default behavior, and not no additional files -- expected no additional files, but I get it... sorta a yaml limitation
• "none" (an non-existent file) That broke the build saying it couldn't find the file - definitely not expected, but I guess I get it
• "none*" -- that worked. Weird.

archive:
  name_template: "{{ .Binary }}_{{ .Version }}_{{ .Os }}_{{ .Arch }}"
  replacements:
    amd64: 64bit
    386: 32bit
    darwin: mac
  files:
    - none*

you can screw around in

git clone https://github.com/client9/misspell.git
cd misspell
./scripts/goreleaser-dryrun.sh

This could be just a documentation bug.

[caarlos0]

hmm, I think this never worked this way, if it did, it was a bug before...

the problem is that the default is set to license and etc, so if you leave it empty it will add those files anyway.

adding the none* works because goreleaser globs it, and since there are no files matching that glob, it works.

not sure what is the right thing to do here...

[client9]

ha! you are right. It always worked that way. I just checked some old packages I made using goreleaser. I never noticed!

might just be a documentation bug... or maybe?? if you put the binary name only in the files section then, that's a special case.

files:
  misspell

means "just the binary" ? Maybe that is less gross than "none*"

really not a big deal either way. I can live with "none*"

[caarlos0]

yeah, I'm not sure as well... looking at the sources, there is not a good retro-compatible way of adding that...

I think none* is the better hack atm :/

[caarlos0]

I'll just point that hack down on the docs...

[Ilyes512]

Is there a reason you choose to use a glob instead of a non glob like:

archive:
  files:
  - none

[caarlos0]

Yes, if you choose a glob that doesn’t match any files, z-glob (lib uses for globs) returns am empty list. If you pass a non-glob and the file doesn’t exist, it returns a file not found kind of error...

If recall correctly, that’s it 🤔

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.