-
Notifications
You must be signed in to change notification settings - Fork 237
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
CLI-only package #793
Comments
To be more precise, I think the problem is with lablgtk2 in Debian Bullseye - we have the following comment in our CI config:
However, lablgtk3 is what CoqIDE uses, so this should be supported across both lots of Linuxes and Windows and Mac. |
Could you edit this to be clearer? Unison is source, not binary packages, and I'm guessing you mean the opam/dune files that are checked in. And, unison has switched to gtk3, so I'm not sure this makes sense against the tip of master. |
The latest release of |
The latest release of unison is 2.52.1, so not sure what's up. But packaging systems are there own thing, and what the opam project does is not really in scope here, just as how pkgsrc, debian, RH, etc. handle unison is their issue. That said, we are heading to 2.53.0 fairly soon. Testing of that is always appreciated. |
The packages available via opam directly ( However, the issue is really unrelated to what exactly is available there, since to even have the possibility of building unison without lablgtk, the source code must have support for this, e.g., via the Dune build system. I presume #671 is a step towards this. |
I still don't entirely follow this. pkgsrc builds unison without a gui. So if it's a feature request to change the dune build files that are in the unison source tree, please either edit or open a new PR and say that clearly. Requests about files in an opam repo should be addressed to them. (From my point of view, dune is something some people use, and is not the primary build system.) |
I ran 'dune build -p unison' and got a CLI-only unison executable. However I see your point that the package file says it needs lablgtk3, even though it actually doesn't. Is that what you mean? |
Please see https://lists.seas.upenn.edu/pipermail/unison-hackers/2022-November/002061.html and followup on the list. |
I have restated the issue (in a way that future me will understand) in #842. |
The current Unison package requires lablgtk, making it incompatible with some Linux distributions per coq/opam#2303 (comment). Consider releasing a CLI-only package.
#671 should fix this.
The text was updated successfully, but these errors were encountered: