You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hard to tell if this is a feature request or a bug.
But since the github releases are well crafted, it would be helpful if the executable would also tell the version, and maybe even the protocol revision ?
The text was updated successfully, but these errors were encountered:
How can cmirror know its version? Mirror the (expected next) version in the sources (Makefile) ? Easy to forget, additional work for every change and easy to get out of sync. As bee doesn't build from git, we can't use git describe --tags, which also has its problems anyway.
I agree that the version info is not that important when using mariux with bee and pdist working hand in hand.
In case you install it on a different *nix, it is helpful to know at what stage /usr/bin/cmirror on some host is. I also agree that there is no simple/straight way to keep the version info of the software and the git-mechanics consistant. OTOH every other software project with public users has to deal with this problem.
Well, i think it is inevitable to do an extra check for the correct version before creating a git-release - in case you want this feature.
Hard to tell if this is a feature request or a bug.
But since the github releases are well crafted, it would be helpful if the executable would also tell the version, and maybe even the protocol revision ?
The text was updated successfully, but these errors were encountered: