From owner-freebsd-ports Mon Feb 17 3:28:41 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A2A737B401 for ; Mon, 17 Feb 2003 03:28:40 -0800 (PST) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D1F843FBD for ; Mon, 17 Feb 2003 03:28:39 -0800 (PST) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from m2a2.dyndns.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 71B3BA381D for ; Mon, 17 Feb 2003 12:28:38 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 8E09C7C405; Mon, 17 Feb 2003 12:28:36 +0100 (CET) To: freebsd-ports@freebsd.org Subject: General: crypto in ports vs. RESTRICTED=... in Makefile From: Matthias Andree Date: Mon, 17 Feb 2003 12:28:36 +0100 Message-ID: User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.2 (i586-suse-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I recently added a "RESTRICTED" tag to ports/databases/db41 and added a db41-nocrypto port that uses the "nocrypto" version of DB 4.1.25.1. Christian "naddy" Weisgerber asked whether this was right, I replied that I took that procedure from the Porter's Handbook (that says crypto code is to be tagged RESTRICTED), and Christian suggested that I take this up on ports then. So here we stand... What's the consensus on tagging ports that contain cryptographic code with "RESTRICTED"? Is this necessary, as documented in the Porter's handbook, or is this obsolete or incorrect (and if so, why, and where documented)? Is the port split into crypto and non-crypto correct? Thanks in advance, -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message