583424 – dev-db/postgresql: use python-r1.eclass instead of python-single-r1.eclassto allow installation of modules for python2 and 3 in parallel

Bug 583424 - dev-db/postgresql: use python-r1.eclass instead of python-single-r1.eclassto allow installation of modules for python2 and 3 in parallel

Summary: dev-db/postgresql: use python-r1.eclass instead of python-single-r1.eclassto ...

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Server (show other bugs)
Hardware:	All Linux

Importance:	Normal enhancement (vote)
Assignee:	PgSQL Bugs

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2016-05-18 17:21 UTC by Gianni Rossi
Modified:	2020-07-24 03:12 UTC (History)
CC List:	0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Gianni Rossi 2016-05-18 17:21:53 UTC

PostgreSQL supports Python extantions for v2 and v3, but the ebuild only permits choosing one.

Reproducible: Always

Steps to Reproduce:
1. emerge postgresql
Actual Results:  
either lib/plpython3u.so or lib/plpython2u.so is built

Expected Results:  
lib/plpython3u.so and lib/plpython2u.so are built

Comment 1 Aaron W. Swenson gentoo-dev

2020-07-24 03:12:46 UTC

Python 2 is going away, but the major hold up of making this work was having to subvert the entire Portage build process in order to make this happen. I never got around to it, and apparently it wasn't in great demand.