-
Notifications
You must be signed in to change notification settings - Fork 185
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
RFE: git tagging/versioning convention #555
Comments
Just to add some context, the tagging/versioning convention is that of Luarocks rockspecs: https://github.com/luarocks/luarocks/wiki/Rockspec-format We're slightly abusing it, though, for sure, since we just inherit the Libuv version and then use the rockspec revision in order to release patches to Luv for a given Libuv version. I believe it's been discussed before to maybe move to some sort of Libuv-version-indepedent versioning, but nothing was ever decided. Is there something specific you're trying to do, just to better understand what the possible solutions are? |
Yep that document as well ignores basic versioning rules used by all packaging software. |
Could you be more specific about what problem you're running into? Linux package managers seem to either include the https://pkgs.org/download/lua-luv (note: all Lua modules published to Luarocks use the rockspec versioning, but not necessarily for their git tags. We tag with the rockspec version because of how we slightly abuse the rockspec version as mentioned previously) |
I'm trying to tell that at the moment it is not possoible to use git tag as version on packaging. |
Which packaging? Is it not possible to specify the git tag and the package version separately? |
Again: none of the packaging software allows use |
Forgive my ignorance here as I'm unfamiliar with the packaging process, but I'm not sure how to square that with the existing https://packages.debian.org/bullseye/lua-luv Here's what the Debian docs have to say:
And here's an rpm package that swapped the https://centos.pkgs.org/8/epel-aarch64/lua-luv-1.36.0.0-1.el8.aarch64.rpm.html EDIT: Here's the Fedora https://src.fedoraproject.org/rpms/lua-luv/blob/rawhide/f/lua-luv.spec Does replacing the |
And as you see it is necessary to perform extra steps to replace that |
The text I quoted is about
This doesn't seem like too large a burden? I feel like I'm missing something. |
Looks like even for Fedora maintainers this is not clear. |
This has already been dis-proven for dpkg, and there are workarounds for package systems which don't allow use of |
Please consider change tagging/versioning convention and replace use
-
by.
because none of the packaging software allows use-
in version string.The text was updated successfully, but these errors were encountered: