Subject: Re: mk/tools/bootstrap.mk forces wrong tar
To: Jeremy C. Reed <reed@reedmedia.net>
From: Johnny Lam <jlam@pkgsrc.org>
List: tech-pkg
Date: 04/11/2006 16:34:06
Jeremy C. Reed wrote:
>
> So I see that mk/tools/tools.DragonFly.mk has:
>
> TOOLS_PLATFORM.tar?= /usr/bin/tar
>
> But it is not used because of mk/tools/bootstrap.mk which sets this first:
>
> .elif ${OPSYS} == "DragonFly"
> TOOLS_PLATFORM.pax?= ${LOCALBASE}/bin/pax
> TOOLS_PLATFORM.tar?= ${LOCALBASE}/bin/tar
>
> My workaround for now is to set "TOOLS_PLATFORM.tar=tar".
>
> I see that mk/tools/bootstrap.mk says "This file should go away".
>
> Should each mk/tools/tools.$OPSYS.mk just check for the existence of
> native and if not then use the bootstrap version if it exists?
>
> What is the plan?
If DragonFly uses its own tar, then remove the definition from
bootstrap.mk so that the one from tools.${OPSYS}.mk can take effect.
Cheers,
-- Johnny Lam <jlam@pkgsrc.org>