In the version of syslog-ocaml that Sylvain just uploaded, I fixed a bug by adding a C stub and a binding to a Linux-specific version of the send(2) system call.
Previously this package produced only libsyslog-ocaml-dev, since it was pure OCaml. Now that it's impure, do I need to produce libsyslog-ocaml also? I can't remember in what situations it's required, and a quick test of a bytecode client of syslog seemed to work fine. The packaging policy seems to say that it's needed, but not *why* it's needed. My second question is somewhat higher level. The bugfix above is Linux-specific, so upstream doesn't want to adopt it (if he moves to some kind of autoconfiguration tool in the future he might). Instead, he'll use the first solution that I came up with, which is pure OCaml but less efficient (installing and removing a Unix signal handler around each write call). Do you think the more efficient version is worth having a Debian-specific patch and (possibly) a 2nd package in the archive? Cheers, Eric -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
