| Summary: | dev-lang/yasm should support installation for multiple Python ABIs | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Arfrever Frehtes Taifersar Arahesis (RETIRED) <arfrever> |
| Component: | Current packages | Assignee: | AMD64 Project <amd64> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | ssuominen |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 308257 | ||
| Attachments: | yasm-1.1.0.ebuild.patch | ||
|
Description
Arfrever Frehtes Taifersar Arahesis (RETIRED)
2010-09-04 22:18:31 UTC
Created attachment 246051 [details, diff]
yasm-1.1.0.ebuild.patch
Looks way too hacky. I rather stick to the upstream build system, and when Python 3 becomes the default python, switch to using it. And there's no point in building for multiple python 2 versions, just support one and make users use the python-updater like normal Some users might develop an application, which uses yasm module. They might want to support e.g. Python 2.5, 2.6 and 2.7 in this application and they would need yasm module installed for multiple Python versions simultaneously to be able to test this application with these Python versions. This patch isn't hacky. It uses standard way of handling of installation for multiple Python versions in such packages. No. The old way of building modules for latest active python version has worked for us for years, i'm not going to add this hack to support the non-existant user group at the expense of copy'n'pasting the code from upstream build system to the ebuild. In fact, I suggest you remove python 2.4, 2.5 from tree entirely. (In reply to comment #5) > The old way of building modules for latest active python version has worked > for us for years And users were complaining (e.g. on Gentoo Forums) that they were unable to install Python modules for multiple Python versions. |