From owner-freebsd-ports@FreeBSD.ORG Tue Jun 28 18:21:34 2005 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D846816A41C for ; Tue, 28 Jun 2005 18:21:34 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9882A43D4C for ; Tue, 28 Jun 2005 18:21:34 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by postfix4-2.free.fr (Postfix) with ESMTP id 777EA32043F for ; Tue, 28 Jun 2005 20:21:33 +0200 (CEST) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id j5SILQ90004448; Tue, 28 Jun 2005 20:21:29 +0200 (CEST) From: Thierry Herbelot To: Jose M Rodriguez Date: Tue, 28 Jun 2005 20:21:23 +0200 User-Agent: KMail/1.8.1 References: <200506281236.08334.thierry@herbelot.com> <200506281435.33658.thierry@herbelot.com> <200506281949.20089.josemi@redesjm.local> In-Reply-To: <200506281949.20089.josemi@redesjm.local> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200506282021.24734.thierry@herbelot.com> Cc: ports@freebsd.org Subject: Symbolic link to the ports tree [was Re: bug in patching phase of cups-pstoraster] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2005 18:21:35 -0000 Le Tuesday 28 June 2005 19:49, Jose M Rodriguez a écrit : > No, that's how this works. I can also point to several ports that uses > this kind of construct that will break without PORTSDIR. > > This is pointed by ports(7) and the notes on ${PORTSDIR}/Mk/bsd.port.mk. I won't argue : I had an issue, and you gave me a solution. I just said my setup was not in contradiction with the instructions in the ports man page (as the default PORTSDIR was correctly pointing to a full ports tree), and the build was still failing > > I can make the construct based on CURDIR, but this is the most often see > form of doing depends. No : your makefile is easier to read with PORTSDIR I have proposed an addition to the man page to avoid this problem in the future (still not completely satisfying as some other people may fall in the same trap as me) > -- > josemi Cheers TfH