Reorganize crypto handling, as discussed on tech-pkg. Remove all

RESTRICTED= variables that were predicated on former U.S. export
regulations. Add CRYPTO=, as necessary, so it's still possible to
exclude all crypto packages from a build by setting MKCRYPTO=no
(but "lintpkgsrc -R" will no longer catch them).

Specifically,

- - All packages which set USE_SSL just lose their RESTRICTED
    variable, since MKCRYPTO responds to USE_SSL directly.
- - realplayer7 and ns-flash keep their RESTRICTED, which is based
    on license terms, but also gain the CRYPTO variable.
- - srp-client is now marked broken, since the distfile is evidently
    no longer available. On this, we're no worse off than before.
    [We haven't been mirroring the distfile, or testing the build!]
- - isakmpd gets CRYPTO for RESTRICTED, but remains broken.
- - crack loses all restrictions, as it does not evidently empower
    a user to utilize strong encryption (working definition: ability
    to encode a message that requires a secret key plus big number
    arithmetic to decode).

1 files changed, 1 insertions, 5 deletions

diff --git a/www/lynx-current/Makefile b/www/lynx-current/Makefile
index e50b5f17ab9..2fda3d0c8f5 100644
--- a/www/lynx-current/Makefile
+++ b/www/lynx-current/Makefile
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.18 2000/08/11 13:18:39 fredb Exp $
+# $NetBSD: Makefile,v 1.19 2000/09/09 19:40:25 fredb Exp $
 #
 
 DISTNAME=		lynx2.8.4dev.7
@@ -27,10 +27,6 @@ HOMEPAGE=		http://lynx.browser.org/
 
 DEPENDS+=		gettext>=0.10.35nb1:../../devel/gettext
 
-RESTRICTED=		"Crypto, export-controlled"
-NO_BIN_ON_FTP=		${RESTRICTED}
-NO_SRC_ON_FTP=		${RESTRICTED}
-
 DIST_SUBDIR=		lynx
 EXTRACT_ONLY=		${DISTFILES:M*.tar.bz2}
 WRKSRC=			${WRKDIR}/lynx2-8-4