-
Notifications
You must be signed in to change notification settings - Fork 31
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
Embeds a modified copy of libyaml #51
Comments
I really appreciate you taking the time to submit this upstream. Debian packaging wins again, thanks @glondu :-) |
+1 here as vendored It might be possible to fix it but, frankly, the module should be able to bind (w/o Thanks for the hard work nonetheless! |
FYI we also came across this problem when packaging ocaml-yaml and we're unbundling it here: https://bugzilla.redhat.com/show_bug.cgi?id=2217729 Basically we patch the system A better solution would be for ocaml-yaml to detect the system libyaml and use it (once the changes above have gone into libyaml). |
Before doing anything about this, I'm generally worried about the state of libyaml upstream maintenance, and several heap overflows reported upstream. Should we just be focussing on a pure OCaml implementation instead of trying to track libyaml? |
I believe this is a case where a native OCaml version could well be better. (A bit surprised there's not one already ...) I'm sure you're aware that yaml is a minefield of a format so good luck! |
I agree with your worries about libyaml upstream maintenance, and that a pure OCaml implementation would be useful. |
Maybe a pure OCaml implementation could be done with https://github.com/yaml/yaml-reference-parser |
While packaging ocaml-yaml for Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001893), I've realized that it embeds a modified copy of libyaml. This is bad, for many reasons including following new versions, and security updates.
The changes look simple and uncontroversial, so I've made a pull request to libyaml: yaml/libyaml#235
I am opening this issue to inform ocaml-yaml authors of this process, and track the effort of making ocaml-yaml buildable with pristine libyaml.
The text was updated successfully, but these errors were encountered: