From owner-freebsd-ports  Tue Aug 29 03:19:44 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id DAA22319
          for ports-outgoing; Tue, 29 Aug 1995 03:19:44 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id DAA22311
          ; Tue, 29 Aug 1995 03:19:41 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id DAA14224; Tue, 29 Aug 1995 03:19:39 -0700
Date: Tue, 29 Aug 1995 03:19:39 -0700
Message-Id: <199508291019.DAA14224@silvia.HIP.Berkeley.EDU>
To: paul@freebsd.org
CC: ports@freebsd.org
In-reply-to: <199508281806.TAA10360@server.netcraft.co.uk> (message from Paul Richards on Mon, 28 Aug 1995 19:06:51 +0100 (BST))
Subject: Re: Dependencies
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: ports-owner@freebsd.org
Precedence: bulk

 * A lot of them don't. We probably need two dependencies, one for
 * ports that need things to build and one that need things in order to run.
 * The first could be fatal the second should not be.

This is a very good point, and actually discussed on this list a while 
ago.  I'll send out a proposal for reorganizing the *_DEPENDS
variables soon (like early next week).

 * If necessary this should be changed to check the existence of the file
 * and whether it's executable, relying on the environment path is
 * not working right.

I think we can make the check a little more "intelligent", for
instance by checking for /usr/local/bin and /usr/X11R6/bin if it's not
in the search path AND the program is not found, and printing out a
warning about them if it's in either one (these two should cover 97%
of our ports).

Satoshi