On Jul 22, 2014, at 3:40 PM, Bill Wohler <wohler(_at_)newt(_dot_)com> wrote:
ncurses and libssl (for sasl and tls) come to mind as well.That's pretty basic. I am surprised that you had to ask IT to install that much extra stuff.Keep in mind that CCBs are once a week, so it's not like it was a lot of libraries.
We do try to keep the external dependencies to the absolute bare minimum. But when the "OS" decides to stop installing such basic core components as termcap/curses, that's not something we are going to get too sympathetic about ... (The irony is that those same systems are almost guaranteed to have installed the hundreds of megabytes of gnome goop.) These days I do think it's reasonable to expect openssl to be present. But not the CMU SASL libraries. My thought has always been that we should include our own bare-bones SASL implementation, sufficient to allow CRAM-MD5 and PLAIN (after a successful TLS negotiation). This would certainly cover off the vast majority of cases where MH needs to talk to an SMTP or Submission server. I'm not sure what the state of the art is in POP servers, as I haven't used one in a couple of decades. --lyndon
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Nmh-workers mailing list Nmh-workers(_at_)nongnu(_dot_)org https://lists.nongnu.org/mailman/listinfo/nmh-workers