Subject: Resolving (ignoring?) buildlink tools in tools' configure
To: None <>
From: john heasley <>
List: tech-pkg
Date: 09/15/2006 20:41:21
I'd like to turn RANCID ( into a package.  But, It's
configure script attempts to determine the location of various tools (mkdir,
diff, perl, expect, etc) to both have proper interpretter lines (#! ...)
and build an appropriate PATH for it's cron script.

Problem is that the first this it finds is the tools that pkgsrc linked/wrapped
in net/rancid/work/.tools/bin.  Just like the problem mentioned in, but that solution
does not seem universal.

Any suggestions on how to ignore, resolve, etc the real tools?