Date: Wed, 29 Sep 2010 22:40:35 -0500 From: Scot Hetzel <swhetzel@gmail.com> To: "Klaus T. Aehlig" <aehlig-bsd@linta.de> Cc: Dmitry Pryanishnikov <lynx.ripe@gmail.com>, freebsd-ports@freebsd.org Subject: Re: Using portmaster with different PYTHON_VERSION Message-ID: <AANLkTikyjxxgkGiYOxtg%2Bn8i4cov-Jb-FJ8THS=3ZNT6@mail.gmail.com> In-Reply-To: <20100929075359.GH10381@curry.linta.de> References: <AANLkTi=EeLhd6H5v_oJz3FWuHKrY7P=Acv0jV=doq8jd@mail.gmail.com> <AANLkTin4BSdumezq-eUg=kkDT_MDtO%2BGS06YoCXDXft3@mail.gmail.com> <20100929072844.GG10381@curry.linta.de> <20100929075359.GH10381@curry.linta.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 29, 2010 at 2:53 AM, Klaus T. Aehlig <aehlig-bsd@linta.de> wrote:
>
> Hi everybody,
>
> sorry for the noise.
>
>> > MASTERDIR= ${.CURDIR}/../py-httplib2
>>
>> shouldn't that be
>>
>> MASTERDIR=${PORTSDIR}/www/py-httplib2
>>
>> Or have I misunderstood something here?
>
> I obviously did. At least the example in porters' handbook and
> all slave ports use ${.CURDIR}/../ Could some help me improve
> my understanding and explain why it is preferable to refer to the
> location of the current port in the file system rathen than to a
> particular port in the ports tree?
>
Using this Makefile:
#
.include "${PORTSDIR}/www/py-httplib2
will cause make to try to access the www/py-httplib2 directory in the
current directory.
The reason is because PORTSDIR has not been defined at this point.
The PORTSDIR variable is defined in /usr/ports/Mk/bsd.port.mk. Also
bsd.port.mk doesn't get included until after the master port's
Makefile gets included.
This is the reason why slave ports use:
MASTERDIR= ${.CURDIR}/../<master port>
.include "${MASTERDIR}/Makefile"
Scot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikyjxxgkGiYOxtg%2Bn8i4cov-Jb-FJ8THS=3ZNT6>