[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

How to handle libssl support?



Hi all,

what's the current policy for packaging software that can optionally 
linked with libssl support? 

For Woody it seemed to be common practice to provide two separate 
packages, one with ssl support enabled and another one with ssl 
support disabled (like fetchmail/fetchmail-ssl or lynx/lynx-ssl).
It seems in Sarge at least some of the crypto crippled versions 
have just vanished into thin air. For example there is no fetchmail 
package without ssl any more. The only fetchmail package in Sarge 
has libssl support enabled without indication in the package name.

Has the crypto policy changed after the Woody release? And more important:
What would be the best practice for new packages that can optionally linked 
with libssl support?

Best regards - Juergen

-- 
GPG A997BA7A | 87FC DA31 5F00 C885 0DC3  E28F BD0D 4B33 A997 BA7A

Attachment: pgpGjWkFxKY2C.pgp
Description: PGP signature


Reply to: