From owner-freebsd-ports@FreeBSD.ORG Thu Aug 26 21:08:17 2004 Return-Path: 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 B597616A4CF for ; Thu, 26 Aug 2004 21:08:17 +0000 (GMT) Received: from smtp.rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id E127543D4C for ; Thu, 26 Aug 2004 21:08:16 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: (qmail 31205 invoked by uid 89); 26 Aug 2004 21:08:15 -0000 Received: from unknown (HELO it.buh.tecnik93.com) (81.196.204.98) by 0 with SMTP; 26 Aug 2004 21:08:15 -0000 Received: from it.buh.tecnik93.com (localhost.buh.tecnik93.com [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with SMTP id 5C4FA2EC; Fri, 27 Aug 2004 00:08:08 +0300 (EEST) Date: Fri, 27 Aug 2004 00:08:08 +0300 From: Ion-Mihai Tetcu To: Ion-Mihai Tetcu Message-Id: <20040827000808.45630425@it.buh.tecnik93.com> In-Reply-To: <20040826235644.44ac5617@it.buh.tecnik93.com> References: <20040826233219.2e77a7d7@it.buh.tecnik93.com> <9C06A4B9B891DB8147E05420@[192.168.1.51]> <20040826235644.44ac5617@it.buh.tecnik93.com> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: Mathieu Arnold cc: ports@FreeBSD.ORG Subject: Re: .include "files/somefile" before .include X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Aug 2004 21:08:17 -0000 On Thu, 26 Aug 2004 23:56:44 +0300 Ion-Mihai Tetcu wrote: > On Thu, 26 Aug 2004 22:41:36 +0200 > Mathieu Arnold wrote: > > > +-Le 26/08/2004 23:32 +0300, Ion-Mihai Tetcu a dit : > > | Hi, > > | > > | > > | Is it legal to include a file from files _before_ including > > | bsd.port.pre.mk ? > > | > > | I need to obtain some long lists ( of DISTFILES and slave ports) and > > | having them in a separate file would make maintenance much more easy. > > | > > | The problem I see is that .CURDIR is not defined; does this break > > | something ? > > > > .CURDIR is an internal make variable, it's not defined by bsd.*.mk : > > > > > > mat $ cat Makefile > > test: > > @echo ${.CURDIR} > > mat $ make test > > /home/mat > > slave-ports-list contains: > SLAVE_PORTS= slave_port 1 \ > slave_port2 \ > .... etc ........ > > .............. > .include "${.CURDIR}/files/slave-ports-list" > .for port in ${SLAVE_PORTS:O} > OPTIONS+= ${port} ....... > .endfor > .include > ............ > > on make it search slave-port-list in / > Same (and expected) if I put ${FILESDIR}/slave-ports-list" Uh, sorry, it's working with ${.CURDIR}/files (and, of course not with FILESDIR), but portlint -CN complain: WARN: Makefile: possible direct use of "files" found. if so, use ${FILESDIR} instead. And I want do do the same for the DISTFILES. So I'm asking if it's OK to do so (e.g. portlint point of view) as I don't want write it all again if it doesn't obey style. > > What problem are you trying to solve ? > > Trying to have some infrastructure to easily maintain a port with about > 1000 distfiles by breaking it in slave ports and having a metaport to > install the small ones. And I have some scripts hat automate the a large part of the process. -- IOnut Unregistered ;) FreeBSD "user"