The new flag `--skip-sign` as the same effect as saying
`artifacts: none`. It lets non GPG key owners (like Travis)
use it.
Signed-off-by: Yoan Blanc <yoan.blanc@exoscale.ch>
This allows users to specify different sets of compiler, assembler,
and/or linker flags for different packages. It also makes it possible to
specify generic flags that contain spaces. It does this while
maintaining compatibility with the old format of the fields in question
by up-converting bare strings into single-element lists.
Resolves#668
assert.NotEmpty() was being used as if it would check multiple
arguments. In actuality, it checks the second argument and, if it
determines that it is empty, fails the test with an error message
containing all subsequent arguments.
Support per-format NFPM overrides (as recently implemented in NFPM),
plus a pair or Goreleaser specific overrides, for "Replacements"
and "NameTemplate" (to address #640).
This keeps backward compatibility with existing config files:
settings at the root of the nfpm config section will still work as
previously (which is also useful to define common/shared settings
that we don't want to override anyway).
If the config file has no entry for caveats, the Caveats field of the
struct defaults to the empty string. When strings.Split() is called on
the empty string, it returns []string{""}. This is considered truthy by
the template processor, resulting in a caveats section consisting of a
blank line.
The #597 added support for customizing the final Brew formula name.
The generated *.rb file still were using the project name as
class name and installing with custom name didn't work.
Fixed the issue by using the `name` field as an input for
building the class name, which defaults to project name
if no name given.
this was first broken in 58307599588f8d9177c62151d5a4e77f83196fe7
and hotfixed in 093291f3ad176f23463103baa3bb254bf96a6773
I believe this is a better fix
