Postgresql82 port installation location weirdness

[Weissmann Markus]

On 12 May 2007, at 09:29, Ryan Schmidt wrote:

> On May 12, 2007, at 02:23, Randall Wood wrote:
>
>> Why is the postgresql82 port installed in the file locations its  
>> installed in?
>>
>> It is spread out strangely, and this making me pull some black  
>> magic to get a port that depends on it working, that I would  
>> rather not do.
>>
>> It installs the following data in the following places:
>> --sysconfdir=${prefix}/etc/${name} \
>> --bindir=${prefix}/lib/${name}/bin \
>> --libdir=${prefix}/lib/${name} \
>> --includedir=${prefix}/lib/${name}/include/${name} \
>>
>> I am porting an autoconf-based package (libgda3) that detects  
>> postgres database libraries in /path/to/postgres/lib and is fairly  
>> inflexible about this.
>>
>> I would like to suggest that maybe we need to create a space in $ 
>> {prefix} where ports that need to be installed in a private  
>> namespace can be installed there, such as ${prefix}/port In the  
>> case of postgresql82, this would mean installing in ${prefix}/port/ 
>> postgresql82 (although I would leave the conf dir where it is at)
>
> The php5 port pulls some black magic to work with the layout of the  
> mysql5 port. It's not too bad.
>

For the common autoconf-based software it is sufficient to just set  
the CFLAGS and LDFLAGS to find the postgresql port in question.
E. g.
configure.cflags "-I${prefix}/lib/postgresql82"
configure.ldflags "-L${prefix}/include/postgresql82"


ciao,

-Markus

---
Markus W. Weissmann
http://www.mweissmann.de/