Should I place the module that provides SSL as a requirement in my Makefile.PL or allow for the user to install it without SSL and die() if a SSL connection is requested and the SSL module is not present ?
Makefile.PL should warn the user if he doesn't have IO::Socket::SSL that it is required for SSL support,
and then go on its merry way.
The SSL tests should be skipped if IO::Socket::SSL is not present.
And yes, if a user tries to make a SSL connection the module should die.
| MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" | | I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). | | ** The third rule of perl club is a statement of fact: pod is sexy. |
| [reply] |
Archive::Tar will install without IO::Zlib, but it is
clearly documented that it can't handle compressed or
gzipped tarballs unless you install IO::Zlib.
Otherwise you can still do regular, non-compressed
tarballs. IMO, this is a good approach.
"In adjectives, with the addition of inflectional endings, a changeable long vowel (Qamets or Tsere) in an open, propretonic syllable will reduce to Vocal Shewa. This type of change occurs when the open, pretonic syllable of the masculine singular adjective becomes propretonic with the addition of inflectional endings."
— Pratico & Van Pelt, BBHG, p68
| [reply] |
I guess it depends on what you're writing, but I say allow the user to install and use the module without SSL. The LWP module works just fine for http without https support. Strongly advise them of the security and need to use SSL in your docs and even during the install and module complilation, but don't prevent them from using your perfectly good module just because they really should use SSL. There are too many political aspects to encryption code to require it. Maybe they'll just pipe your module over an SSH tunnel or VPN and have encryption. | [reply] |
