Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[request] automatic file names #70

Closed
costela opened this issue Sep 20, 2019 · 3 comments
Closed

[request] automatic file names #70

costela opened this issue Sep 20, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@costela
Copy link

costela commented Sep 20, 2019

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:

{{ 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.

@mig4
Copy link

mig4 commented Oct 30, 2019

not sure if there's an equivalent convention on the RPM side

sure there is: {{ name }}-{{ version }}-{{ release }}.{{ disttag }}.{{ arch }}.rpm

I agree, this would be good 👍

@caarlos0 caarlos0 added the enhancement New feature or request label Jan 15, 2020
@erikgeiser
Copy link
Member

I think this can be closed now after #157 was merged. I did not notice this issue when I created the pull request so I didn't reference it.

@caarlos0
Copy link
Member

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.

@goreleaser goreleaser locked as resolved and limited conversation to collaborators Nov 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants