Summary: | Propose dxr3 USE variable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Arcady Genkin (RETIRED) <agenkin> |
Component: | [OLD] Core system | Assignee: | Seemant Kulleen (RETIRED) <seemant> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | lostlogic |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 2214 |
Description
Arcady Genkin (RETIRED)
2002-04-29 02:33:07 UTC
The only specific applications that need this variable are mplayer and xine, however it is fairly important that it exist for reasons such as those discussed in bug 2214 wherein the latest xine breaks if it tries to compile the automatically detected dxr3 support. Well, technically, that sort of situation can be fixed by disabling dxr3 support in the xine ebuild for *everybody*. That won't hurt the people who are not using dxr3, and will help the people who have the dxr3 libraries installed to get the broken application compiled. However, it may still be a good idea to have dxr3 in the USE variable. I dunno. brandon, arcady: this still an issue? lostlogic> seemant: you can probably close it, seems that most users and the xine/mplayer people are making it autodetect acceptably |