Hi,

Sorry for the late response. I can confirm that it did not break
anything on Fedora 15 and RHEL 6.

Regards,
Devrim

On Thu, 2011-09-22 at 11:39 -0400, Steve Singer wrote:
> In 2.1.0 and 2.0.7 we stopped linking slonik against pgport on non win32 
> platforms because many people were complaining that their postgresql 
> packages didn't include libpgport.a
> 
> In many versions of slony 1.2.x slonik would use the postgresql pgport 
> function find_my_exec to determine the runtime location of the slony 
> binary in order to determine the location of the share directory.  Some 
> packagers have now complained that the location the slony binaries will 
> be installed into at install time can't be known at compile time.
> 
> I am proposing the attached patch that uses a configure flag+check to 
> decide if pgport is available at compile time it will call find_my_exec 
> at runtime. Otherwise it falls back to the compile time pgshare.
> 
> Does this accomplish what is required without breaking anything new?
> 
> https://github.com/ssinger/slony1-engine/commit/93e097242ad8be5364fe481f7eff063d408e09d2
> 


-- 
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.slony.info/pipermail/slony1-hackers/attachments/20111021/17200f13/attachment.pgp