From owner-freebsd-ports  Tue Aug  6 16:20:25 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA12285
          for ports-outgoing; Tue, 6 Aug 1996 16:20:25 -0700 (PDT)
Received: from sunrise.cs.berkeley.edu (root@sunrise.CS.Berkeley.EDU [128.32.38.121])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA12167
          for <FreeBSD-Ports@FreeBSD.org>; Tue, 6 Aug 1996 16:19:54 -0700 (PDT)
Received: (from asami@localhost) by sunrise.cs.berkeley.edu (8.7.5/8.6.12) id QAA02582; Tue, 6 Aug 1996 16:19:30 -0700 (PDT)
Date: Tue, 6 Aug 1996 16:19:30 -0700 (PDT)
Message-Id: <199608062319.QAA02582@sunrise.cs.berkeley.edu>
To: narvi@haldjas.folklore.ee
CC: FreeBSD-Ports@FreeBSD.org
In-reply-to: <Pine.BSF.3.91.960803204356.218L-100000@haldjas.folklore.ee> (message from Narvi on Sat, 3 Aug 1996 21:27:14 +0300 (EET DST))
Subject: Re: Proposal for a new bsd.port.mk variable.
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

 * I would like to make a proposal for a new bsd.port.mk dependency 
 * variable, EXTRACT_DEPENDS.

>From the latest handbook:

===
BUILD_DEPENDS

This variable specifies executables this port requires to build. Like
RUN_DEPENDS, it is a list of `exec:dir' pairs. For example,

      BUILD_DEPENDS=   unzip:${PORTSDIR}/archivers/unzip

will check for an executable called `unzip', and descend into the
archivers/unzip subdirectory of your ports tree to build and install
it if it is not found.

Note that `build' here means everything from extracting to
compilation. The dependency is checked from within the extract target.
===

So it's there. :)

Satoshi