-
Notifications
You must be signed in to change notification settings - Fork 39
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
Tag stable releases? #101
Comments
Sorry for the delay; yeah, that's not an issue at all. I'll try to get these tagged today. They'll be Also hopefully 13 support. |
@rpav did you mean to create the tag i'd recommend a different tag pattern: sidenote: this is what i was doing for the guix packaging before i learned about c2ffi tags (but it also includes the git hash: and while we are at it, i would also only use the LLVM major version here and for the branch name. |
FYI, c2ffi is now available in Guix, and uses the newly introduced git tags: https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8c303758590e368fc6a67bfff8dd1721e70afd93 |
My Homebrew package for C2FFI was just rejected from Homebrew Core (Homebrew/homebrew-core#86127) because C2FFI does not have individual tagged releases. While there is a stable branch, individual versions are not tagged, and the Homebrew maintainers do not want to support packaging software with that kind of release program.
I will probably run into similar issues when trying to package C2FFI for other package managers and platforms. Would you consider tagging some "stable" releases within each branch, to facilitate packaging? This would make it a lot easier for people to use CFFI, especially given that it can be non-trivial to compile on MacOS.
The text was updated successfully, but these errors were encountered: