-
Notifications
You must be signed in to change notification settings - Fork 184
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
Using of dynamic vMajor.Minor tags #318
Comments
In a perfect world yes, but mistakes are easily made. Tbh I prefer strict versioning as it would guarantee reproducibility in all circumstances. Perhaps an auto-update feature (that would override the version in cmake or in a version lock file) would be nice instead. |
Maybe a |
In general I think it's a nice idea, however should come together with proper lockfile support so that we can still commit exact versions into our repositories. |
Currently its rather tedious tkeeping all projects using CPM up2date. I use the
get_cpm
module, which works quite nice. I think it would be a great improvement, if CPM keeps additional dynamicvMajor.Minor
tags, which will then be moved to the current active patch tag. These tags could then be targeted by theget_cpm
module.Image a tag
v0.42
. Then patchv0.42.1
comes out and thev0.42
tag will be reset to point exactly to the same commit as thev0.42.1
. But it will not move to av0.43.x
patch.As patches usually don't break anything but patches bugs, that should be a preferable behaviour.
The text was updated successfully, but these errors were encountered: