Date: Wed, 29 Sep 2010 09:53:59 +0200 From: "Klaus T. Aehlig" <aehlig-bsd@linta.de> To: Scot Hetzel <swhetzel@gmail.com> Cc: Dmitry Pryanishnikov <lynx.ripe@gmail.com>, freebsd-ports@freebsd.org Subject: Re: Using portmaster with different PYTHON_VERSION Message-ID: <20100929075359.GH10381@curry.linta.de> In-Reply-To: <20100929072844.GG10381@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Best reagrds and please excuse my last mail.
Klaus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100929075359.GH10381>