Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 359361 - app-admin/eselect-postgresql-0.3 does not set correct path for libpq.so.5
Summary: app-admin/eselect-postgresql-0.3 does not set correct path for libpq.so.5
Status: RESOLVED DUPLICATE of bug 352147
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: PgSQL Bugs
URL:
Whiteboard:
Keywords:
: 359989 360043 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-03-18 12:56 UTC by Graham Murray
Modified: 2011-04-01 15:42 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Murray 2011-03-18 12:56:49 UTC
When there are multiple versions of postgresql-base installed, 'eselect postgresql set' is supposed to select which version is active. For the most part this works OK, but it does not correctly handle setting the library path. The problem is that /etc/env.d/ contains files 50postgresql-94-maj.min for each installed version, and each of these sets the LDPATH to its version of the library directory. This results in applications (other than those which are part of postgresql, which have  the appropriate rpath set) loading the lowest installed version at runtime. 

'eselect postgresql set' should ensure that only the correct version's library directory is on the loader path.
Comment 1 Aaron W. Swenson gentoo-dev 2011-03-19 22:06:16 UTC
Please review app-admin/eselect-postgresql-1.0.3. It should address this issue.
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2011-03-22 18:42:12 UTC
*** Bug 359989 has been marked as a duplicate of this bug. ***
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2011-03-23 16:58:49 UTC
*** Bug 360043 has been marked as a duplicate of this bug. ***
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2011-04-01 15:42:43 UTC

*** This bug has been marked as a duplicate of bug 352147 ***