From owner-freebsd-ports Fri Jun 26 14:42:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10738 for freebsd-ports-outgoing; Fri, 26 Jun 1998 14:42:53 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10608; Fri, 26 Jun 1998 14:42:12 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.7/8.7.3) id OAA08935; Fri, 26 Jun 1998 14:42:02 -0700 (PDT) Date: Fri, 26 Jun 1998 14:42:02 -0700 (PDT) Message-Id: <199806262142.OAA08935@vader.cs.berkeley.edu> To: steve@FreeBSD.ORG CC: gmarco@giovannelli.it, ports@FreeBSD.ORG In-reply-to: <359357B6.FB67F873@scotty.masternet.it> (message from Gianmarco Giovannelli on Fri, 26 Jun 1998 10:11:34 +0200) Subject: Re: P5-Apache : are there any troubles with it ? From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * I think the problem is related to the fact that the port now is apache12 * (or apache13) and not apache only. Steve, can you fix the port? In fact, this port does something very weird: === pre-configure: @ cd ${PORTSDIR}/www/apache && ${MAKE} clean patch === That should be BUILD_DEPENDS=/nonexistent:${PORTSDIR}/www/apache12:patch unless it specifically needs the apache port to be in the post-patch, pre-configure stage. If that is the case, it is very bad for this port's *build* to wipe out a source tree of another port. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message