From owner-freebsd-current Fri Mar 31 0:46:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2FAAC37B744 for ; Fri, 31 Mar 2000 00:46:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA98681; Fri, 31 Mar 2000 00:47:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Bill Fenner Cc: current@freebsd.org Subject: Re: So, AGAIN, why was tcpdump moved? In-reply-to: Your message of "Fri, 31 Mar 2000 00:40:10 PST." <200003310840.AAA02751@windsor.research.att.com> Date: Fri, 31 Mar 2000 00:47:20 -0800 Message-ID: <98671.954492440@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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? Correct! Both would share some common set of sources with VPATH directives and install conditionally on some boolean set of variable tests where one would always succeed and one always fail unless it was the distribute target being invoked, in which case both would install with different values for DISTRIBUTION and not collide. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message