506328 – sys-apps/portage: please add support for PYTHON_TARGETS=pypy

Bug 506328 - sys-apps/portage: please add support for PYTHON_TARGETS=pypy

Summary: sys-apps/portage: please add support for PYTHON_TARGETS=pypy

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-03-31 06:01 UTC by Michał Górny
Modified:	2016-02-02 06:17 UTC (History)
CC List:	1 user (show)

See Also:	506158
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 Michał Górny archtester

2014-03-31 06:01:19 UTC

We're moving away from versioned pypy PYTHON_TARGETS, and instead will be using PYTHON_TARGETS=pypy. Normally I'd handle this through plain PYTHON_COMPAT update but since sys-apps/portage is a big pile of hacks and duplication, I have no idea how to do it properly.

PYTHON_TARGETS=pypy implies:

- dep on virtual/pypy:0= (with slot op)

- interp at /usr/bin/pypy (no -c, no version)

- files at /usr/$(get_libdir)/pypy (no version)

Please do not remove PYTHON_TARGETS=pypy2_0 yet since we need to fix rev-deps first.

Comment 1 Marek Behún 2016-02-02 04:38:20 UTC

Anything new with this?

Comment 2 Brian Dolbec (RETIRED) gentoo-dev

2016-02-02 06:17:58 UTC

All but the old portage-2.2.8-r2 ebuild are pypy enabled.

2.2.8 is only remaining for older system upgrade purposes.

Too many bugs to remember them all...