Date: Tue, 13 Sep 2011 20:25:38 +0400 From: h h <aakuusta@gmail.com> To: Erwin Lansing <erwin@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Is WRKDIR a user- or a port-defined variable? (Re: Screwy behavior in ports framework) Message-ID: <86vcswjtod.fsf_-_@gmail.com> In-Reply-To: <20110913113322.GX79144@droso.net> (Erwin Lansing's message of "Tue, 13 Sep 2011 13:33:22 %2B0200") References: <20110913094514.071C8106573A@hub.freebsd.org> <20110913113322.GX79144@droso.net>
next in thread | previous in thread | raw e-mail | index | archive | help
(redirect from -current@ to -ports@)
Erwin Lansing <erwin@FreeBSD.org> writes:
> On Tue, Sep 13, 2011 at 09:45:05AM +0000, Thomas Mueller wrote:
>>
>>
>> PORTSDIR=/BETA1/usr/ports
>> PACKAGES=/usr/packages
>> WRKDIR=workb2
>> # added by use.perl 2011-09-13 02:49:43
>> PERL_VERSION=5.14.1
>>
>> Maybe WRKDIR should have been ${MASTERDIR}/workb2 , or should it be ${.CURDIR}/workb2 ?
>
> The latter. Default for WRKDIR is ${WRKDIRPREFIX}${.CURDIR}/work, so
> you'll need to include ${.CURDIR} as well.
If it's supported why WRKDIR assignments are not cleaned up?
databases/jasperserver/Makefile:WRKDIR= ${WRKDIRPREFIX}${.CURDIR}/work
misc/py-xdelta3/Makefile:WRKDIR= ${WRKDIRPREFIX}${MASTERDIR}/work
net/py-miniupnpc/Makefile:WRKDIR= ${WRKDIRPREFIX}${MASTERDIR}/work
In fact, Porter's Handbook encourages its redefining unlike WRKDIRPREFIX
http://www.freebsd.org/doc/en/books/porters-handbook/porting-wrkdir.html
http://www.freebsd.org/doc/en/books/porters-handbook/porting-wrkdirprefix.html
Are you talking about new policy?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86vcswjtod.fsf_-_>