Subject: Re: Accurately determining PKGNAME in mk.conf
To: None <firstname.lastname@example.org>
From: Joerg Sonnenberger <email@example.com>
Date: 07/31/2007 17:08:13
On Tue, Jul 31, 2007 at 05:03:56PM +0200, Julio M. Merino Vidal wrote:
> >Why can't you just use the PKGPATH (e.g. via .CURDIR) like everyone
> Because that is ugly? I'd much much rather have a "PKGDIR" variable
> that tells me the package I'm building (x/y) than have to deduce that
> from .CURDIR.
That was not so much the point of the question :-) We can certainly
provide PKGPATH much earlier, but the question was, if that is enough.