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

[FR]: Create Packages on every release (Debian, RPM, etc.) #4686

Open
AndrewQuijano opened this issue Dec 22, 2024 · 1 comment · May be fixed by #4687
Open

[FR]: Create Packages on every release (Debian, RPM, etc.) #4686

AndrewQuijano opened this issue Dec 22, 2024 · 1 comment · May be fixed by #4687

Comments

@AndrewQuijano
Copy link

Does the feature exist in the most recent commit?

No

Why do we need this feature?

This feature would make it easier for anyone to download the latest Debian/RPM package from GitHub rather than have to compile it.

Also, the current versions of GoogleTest, while functional are old (v1.11.0 is from June 2021)
Image

This would also make it easy for consistently having Debian/Ubuntu repositories updated if a package is generated each release.

Describe the proposal.

I think the easiest solution would be to create a CPackConfig.txt to leverage your CMakeLists.txt file. Once this is done, create a GitHub workflow such that on every release, you create the packages and upload it for release. A workflow like the one listed below should do the trick, except you would be using CMake and cpack -G DEB, etc. for each package.

https://github.com/capstone-engine/capstone/blob/next/.github/workflows/build_release.yml

I have a working example on how to create Debian and RPM packages already using CPackConfig.txt here

capstone-engine/capstone#2590

Is the feature specific to an operating system, compiler, or build system version?

For now, start with Linux, but it would be nice to attempt other Operating Systems too.

@Yankuba-debug
Copy link

Good

@AndrewQuijano AndrewQuijano linked a pull request Dec 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants