From owner-freebsd-current Fri Mar 31 0:41:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id D3A8337BA52 for ; Fri, 31 Mar 2000 00:41:08 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id 1BE1D1E00A; Fri, 31 Mar 2000 03:41:05 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id DAA02366; Fri, 31 Mar 2000 03:41:01 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id AAA02751; Fri, 31 Mar 2000 00:40:11 -0800 (PST) Message-Id: <200003310840.AAA02751@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: jkh@zippy.cdrom.com Subject: Re: So, AGAIN, why was tcpdump moved? Cc: fenner@research.att.com, current@freebsd.org Date: Fri, 31 Mar 2000 00:40:10 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >That said, isn't there some way we could build it twice, once for the >crypto dist and once for the bindist? That would mean that the crypto >distribution copy simply blops over the bin distribution version if >selected and POLA is fully obeyed. Sounds perfectly reasonable to me. I'd be happy if someone else wants to look at this, or I can look at it on the 10th when I get back from Australia. This would mean there's a src/secure/usr.sbin/tcpdump that builds with crypto and src/usr.sbin/tcpdump that builds without? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message