Date: Sat, 6 Jun 2009 02:44:37 +0300 From: Vitaly Magerya <vmagerya@gmail.com> To: Ion-Mihai Tetcu <itetcu@freebsd.org> Cc: Eitan Adler <eitanadlerlist@gmail.com>, freebsd-ports@freebsd.org Subject: Re: Automatically generate symlinks for virtual categories. Message-ID: <accd96830906051644m2ee92fd5j80fa8b05c36566c4@mail.gmail.com> In-Reply-To: <20090606013524.7ccc4ede@it.buh.tecnik93.com> References: <4A28590D.101@gmail.com> <accd96830906050419k7ef2469tb1bb22aad4956fe0@mail.gmail.com> <accd96830906050556m660e63cw3c14edfb7f526796@mail.gmail.com> <4A2946F4.2010501@gmail.com> <accd96830906051038m47104ec1oa79c938949e5ca3e@mail.gmail.com> <4A29683C.3030301@gmail.com> <accd96830906051306j3423727bgab9175207805041a@mail.gmail.com> <4A2994DF.1060604@gmail.com> <4A299843.8030407@gmail.com> <20090606013524.7ccc4ede@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/06/2009, Ion-Mihai Tetcu <itetcu@freebsd.org> wrote:
> Did you test what happens with all this idea when a port has a
> .include "${CURDIR}......"
> ?
When running the script uses $(make <opts> -C<port-directory>),
which in effect is $(cd <port-directory> && make <opts>), so
including current directory works fine when symlinks are generated.
When actually installing the port from a symlink,
the current directory is reported to be the original, not the symlink.
So it should work. I've tried a few ports with .include ${CURDIR..},
there seems to be no problems.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?accd96830906051644m2ee92fd5j80fa8b05c36566c4>