Summary: | dev-libs/libclc: invalid USE flags check | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Kurakin <kuraga333> |
Component: | Current packages | Assignee: | LLVM support project <llvm> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | jstein, kuraga333, mgorny, x11 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexander Kurakin
2023-01-13 17:40:51 UTC
Well, yes, the code is wrong. However, I'm not sure whether we should indeed enforce this via REQUIRED_USE or perhaps remove it entirely. @x11, any opinion? libclc is currently only used by mesa[opencl]. Is there a semi-valid use case for installing mesa[opencl] but not enabling any backend on libclc? I'm particularly wondering whether: a. it's better to enforce at least one backend, so that people notice if they're building libclc without any backend and wouldn't end up WTF-ing why something doesn't work, or b. it's better to let people install libclc without any backend, so if it gets pulled in as a dependency but they don't need it, they don't have to go through special hassle. Sorry about my foreign opinion but isn't more important whether the upstream allows such situation? (Mistakenly or not -0 is another question.) I perceive Gentoo as close-to-upstream (a source-based distribution). |