On Fri, 26 Jul 2002 18:10:20 -0400
"Amitai Schlair" <schmonz@schmonz.com> wrote:

> You don't need to (and probably shouldn't) include pyversion.mk
> directly. Instead, include either application.buildlink.mk or
> extension.buildlink.mk (or both, in some cases), and they will include
> pyversion.mk for you.

Ok.

> I'd recommend fixing those paths in two steps. First, patch the
> problematic instances of "python" to @PYTHONBIN@. Then, override the
> pre-configure target and use sed to replace @PYTHONBIN@ with
> ${PYTHONBIN}.

Nice. Although, I've taken a look to application.buildlink.mk and it already
does some kind of replacement, but only in the #! lines of the script. Would
this be extended to also look for and replace @PYTHONBIN@ automatically?

Thanks!


-- 
HispaBSD admin - http://www.HispaBSD.org
Julio Merino <jmmv@hispabsd.org>