postgresql-base is compiled with --without-python, set in the ebuild. Adding a "python" USE flag can set the --with-ptyhon flag, installing some files needed to build python-based PostgreSQL extensions. Reproducible: Always
What are the PostgreSQL extensions?
Multicorn, for example (http://multicorn.org/), needs a Makefile that is only installed if postgresql-base is compiled --with-python.
Foreign Data Wrappers, like Multicorn, require the executor and planner found in dev-db/postgresql-server which can have Python support enabled there.
The compilation of Multicorn needs to find the python flags set in /usr/lib/postgresql-9.1/lib/pgxs/src/Makefile.global, which is installed by postgresql-base (not by postgresql-server). The --with-python flag of postgresql-base sets these flags in Makefile.global.
Sorry to resurrect an old bug, but I think the pg_config utility, as well as the generated Makefiles, need to be in sync with the postgresql server. This is not the case right now, since different options can be used in the configure script from one and the other. It is obvious with this case of "--without-python" hardwritten in the postgresql-base ebuild. The whole postgresql extension system (PGXS) is built around the pg_config utility, and the various generated Makefiles, and as such I think it is very important to keep them in sync. Could you please reconsider reopening/fixing this bug ?
Looks like a valid bugreport to me ...
Created attachment 351990 [details, diff] Unify configuration of postgresql-base and postgresql-server Please find attached a patch which uses the same configuration for building postgresql-base and postgresql-server. In addition to that, postgresql-server also install the pg_regress utility which can be useful for extension developer.
(In reply to Ronan Dunklau from comment #7) > Created attachment 351990 [details, diff] [details, diff] > Unify configuration of postgresql-base and postgresql-server > > Please find attached a patch which uses the same configuration for building > postgresql-base and postgresql-server. > > In addition to that, postgresql-server also install the pg_regress utility > which can be useful for extension developer. Thank you for your eagerness, but it is incomplete. Further, hijacking a bug for a separate issue is not okay. Please see my work-in-progress: https://github.com/titanofold/titanofold-gentoo-x86/tree/master/dev-db/postgresql I'm actively working on several issues in parallel, but real life got in the way the past few weeks. While I welcome patches and help for PostgreSQL-related packages, it needs to be a coordinated effort. You can contact me by email, IRC (TitanOfOld or TitanOfOld|work), or Google+.
*postgresql-base-9.3.0-r1 (15 Sep 2013) *postgresql-base-9.2.4-r1 (15 Sep 2013) *postgresql-base-9.1.9-r1 (15 Sep 2013) *postgresql-base-9.0.13-r1 (15 Sep 2013) *postgresql-base-8.4.17-r1 (15 Sep 2013) 15 Sep 2013; Aaron W. Swenson <titanofold@gentoo.org> +postgresql-base-8.4.17-r1.ebuild, +postgresql-base-9.0.13-r1.ebuild, +postgresql-base-9.1.9-r1.ebuild, +postgresql-base-9.2.4-r1.ebuild, +postgresql-base-9.3.0-r1.ebuild, postgresql-base-9999.ebuild: Add Python support for clients and libraries. Fixes bug 392673. *postgresql-server-9.3.0-r1 (15 Sep 2013) *postgresql-server-9.2.4-r1 (15 Sep 2013) *postgresql-server-9.1.9-r1 (15 Sep 2013) *postgresql-server-9.0.13-r1 (15 Sep 2013) *postgresql-server-8.4.17-r1 (15 Sep 2013) 15 Sep 2013; Aaron W. Swenson <titanofold@gentoo.org> +postgresql-server-8.4.17-r1.ebuild, +postgresql-server-9.0.13-r1.ebuild, +postgresql-server-9.1.9-r1.ebuild, +postgresql-server-9.2.4-r1.ebuild, +postgresql-server-9.3.0-r1.ebuild, postgresql-server-9999.ebuild: Add Python support for clients and libraries. Fixes bug 392673.
