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
nfpm is great, but maybe it would be even greater if it supported automatically naming the generated files.
At least in the deb context, the filename usually has a standardized structure, roughtly:
{{ name }}_{{ version }}_{{ arch }}.deb
Where name is lowercased and basically piped through s/[^a-z]/-/g.
This would make it easier to use generated files with various Debian/Ubuntu package handling tools that assume this format is used.
I'm unfortunately not sure if there's an equivalent convention on the RPM side.
Maybe allow passing --target deb as a sign that the filename should be generated? Or if that's too implicit, a separate flag?
I'm aware that the feature overlaps with what goreleaser's name_template, but IMHO this would still be useful as a feature in nfpm itself.
The text was updated successfully, but these errors were encountered:
Hi,
nfpm is great, but maybe it would be even greater if it supported automatically naming the generated files.
At least in the
deb
context, the filename usually has a standardized structure, roughtly:Where
name
is lowercased and basically piped throughs/[^a-z]/-/g
.This would make it easier to use generated files with various Debian/Ubuntu package handling tools that assume this format is used.
I'm unfortunately not sure if there's an equivalent convention on the RPM side.
Maybe allow passing
--target deb
as a sign that the filename should be generated? Or if that's too implicit, a separate flag?I'm aware that the feature overlaps with what goreleaser's
name_template
, but IMHO this would still be useful as a feature innfpm
itself.The text was updated successfully, but these errors were encountered: