Date: Thu, 26 Aug 2004 23:56:44 +0300 From: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> To: Mathieu Arnold <mat@FreeBSD.org> Cc: ports@FreeBSD.ORG Subject: Re: .include "files/somefile" before .include <bsd.port.pre.mk> Message-ID: <20040826235644.44ac5617@it.buh.tecnik93.com> In-Reply-To: <9C06A4B9B891DB8147E05420@[192.168.1.51]> References: <20040826233219.2e77a7d7@it.buh.tecnik93.com> <9C06A4B9B891DB8147E05420@[192.168.1.51]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Aug 2004 22:41:36 +0200
Mathieu Arnold <mat@FreeBSD.org> 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 <bsd.port.pre.mk>
............
on make it search slave-port-list in /
Same (and expected) if I put ${FILESDIR}/slave-ports-list"
> 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.
Thanks,
--
IOnut
Unregistered ;) FreeBSD "user"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040826235644.44ac5617>