From owner-freebsd-ports Thu Oct 5 19:10:56 1995 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA03895 for ports-outgoing; Thu, 5 Oct 1995 19:10:56 -0700 Received: from forgery.CS.Berkeley.EDU (forgery.CS.Berkeley.EDU [128.32.33.75]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA03889 for ; Thu, 5 Oct 1995 19:10:49 -0700 Received: (from asami@localhost) by forgery.CS.Berkeley.EDU (8.6.11/8.6.9) id TAA18875; Thu, 5 Oct 1995 19:12:25 -0700 Date: Thu, 5 Oct 1995 19:12:25 -0700 Message-Id: <199510060212.TAA18875@forgery.CS.Berkeley.EDU> To: adam@veda.is CC: ports@freebsd.org In-reply-to: <199510051333.NAA26157@veda.is> (message from Adam David on Thu, 5 Oct 1995 13:32:59 +0000 (GMT)) Subject: Re: nntp dependency From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-ports@freebsd.org Precedence: bulk * Was ctime chosen as a random executable belonging to cnews? * Wouldn't it be better to depend on ${PREFIX}/lib/libcnews.a and * ${PREFIX}/include/dbz.h although they are not executable? Is there * any reason why BUILD_DEPENDS should not also be used for static * libraries and library header files needed during the build? What is * a suitable way of depending on both the library and the header file * without causing the depended port to be made twice? Yes. I don't think it makes any difference. Yes, because it uses "which", which looks for executables only. I don't understand the "made twice" part, and I'm sure BUILD_DEPENDS handles it fine. * Is there an accepted convention for substituting variables such as * ${PREFIX} into patchfiles? This port currently has /usr/local * hardcoded at a deeper level, and I suspect there are other ports * that suffer from the same problem. The default do-build target will pass down PREFIX in the environment so if you can pick it up from there, it will be fine. Just do a "CFLAGS += -DPREFIX=${PREFIX}" or something in the Makefile. Satoshi