Writing portfiels: How to avoid hardcoded paths?

[Ryan Schmidt]

On Mar 13, 2008, at 14:15, Giorgio Valoti wrote:

> Hi all, with the help of William Siegrist I wrote a portfile for  
> pgpool-II (ticket #14647). I’ve added the following environment  
> setting:
> configure.env           PATH=$env(PATH):${prefix}/lib/postgresql83/bin
>
> In order to make pg_config available at configure time. Is there a  
> way to avoid hard coding the path?

Is there an option in the configure script for pgpool-II to tell it  
where postgresql is located? Take a look at its "./configure --help"

If not, then I guess you'll have to munge the PATH like that. Which  
isn't awful.