-
Notifications
You must be signed in to change notification settings - Fork 3
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
this repo is out of date and linked to by unison #1
Comments
I determined "out of date" by not having been changed since the most recent release. If that's wrong, it would be good to update to readme to be clearer about what's going on and the scope of how this works. It looks like this is only workable on machines that can run an arch x86-64 container via docker, which obviously is not universal -- and if I were more docker-clueful I'd understand, but that's not how it is. really my point is that I don't want the unison wiki to point to something unless a new person without a lot of clue about the underlying issues will end up knowing whether or not they are running an up-to-date version |
I removed the version for archlinux in the Dockerfile, so the unison-version should be up to date. |
As of 2.52.0 the ocaml version is irrelevant to interop. So the readme needs updating, or at least qualifying that ocaml only matters if interoperating with very old versions. So if someone uses this, following the instructions, today, what unison version do they get? I am not trying to remove if not out of date. I am just underclued. It woudl be nice if the README explained about versions. I think it's that whatever is current in arch is what you get. |
I updated the unison wiki description to say that it isn't really clear what you get with this repo. I'll leave it at that, but if you clarify it, I'll have a look and adjust wording. |
I do not mean to demand that this be kept up to date, but given that it isn't I intend to delink it from:
https://github.com/bcpierce00/unison/wiki/Obtaining-Unison-Sources-and-Binaries
As you probably know, the unison project is cranky about old releases in that it is not allowed to file issues about them.
Please let me know if
Thanks,
Greg [unison maintainer]
The text was updated successfully, but these errors were encountered: