-
Notifications
You must be signed in to change notification settings - Fork 3
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
Makefile: Add recipe to generate "dev" packages #477
Labels
builds
enhancement
New feature or request
packages
Related to generated packages for this project (e.g., RPM, DEB)
Milestone
Comments
atc0005
added
the
packages
Related to generated packages for this project (e.g., RPM, DEB)
label
Feb 2, 2023
Yes. The generated package name (filename and internal name) should also be different to allow both stable and unstable/testing/dev packages to be installed at the same time. |
atc0005
added a commit
that referenced
this issue
Feb 8, 2023
Provide Makefile recipe to allow building "dev" release packages that install alongside stable release versions. This is intended to allow sysadmins to test upcoming features alongside existing stable versions. Other changes: - renamed Makefile variable to better communicate purpose - simplify cleanup recipe step for removing empty asset dirs refs GH-477
atc0005
changed the title
Update Makefile: Add recipe to generate "dev" packages
Makefile: Add recipe to generate "dev" packages
Feb 9, 2023
This was referenced Mar 1, 2023
This was referenced Apr 9, 2023
This was referenced Apr 14, 2023
25 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
builds
enhancement
New feature or request
packages
Related to generated packages for this project (e.g., RPM, DEB)
Overview
On a Nagios box I'm currently using a copy of the plugin named
check_cert_dev
. I'd like to generate "test" or "dev" DEB and RPM packages that deploy files with these names:check_cert_dev
lscert_dev
certsum_dev
To make things easier, it's probably worth adding this as a separate Makefile recipe that uses a separate nFPM config file.
There are probably some pre-release related nFPM settings that I can specify to further make it clear that the generated packages are not for production use.
All of this said, it's probably worth adding a
dev-build
Makefile recipe that does everything the (soon to be added)release-build
recipe does, but with naming/labeling that makes it clear it's not a "stable" release.References
The text was updated successfully, but these errors were encountered: