| Summary: | media-libs/mesa: Package the Amber branch | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Matt Turner <mattst88> |
| Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gentoo+bugs, sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 861023 | ||
| Bug Blocks: | |||
|
Description
Matt Turner
2022-05-09 16:35:20 UTC
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7a9172096b2a7132f66f6baa5b54698774e6d0fb commit 7a9172096b2a7132f66f6baa5b54698774e6d0fb Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2022-05-09 15:12:12 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2022-05-09 17:09:33 +0000 media-libs/mesa: Add SLOT="amber" branch Bug: https://bugs.gentoo.org/843440 Signed-off-by: Matt Turner <mattst88@gentoo.org> media-libs/mesa/mesa-21.3.8-r1.ebuild | 203 ++++++++++++++++++++++++++++++++++ 1 file changed, 203 insertions(+) The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=42941e7b5198931e1c2b6ad460e80596275fbab2 commit 42941e7b5198931e1c2b6ad460e80596275fbab2 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2022-05-12 18:11:38 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2022-05-12 18:18:05 +0000 media-libs/mesa-amber: Add new package Move from media-libs/mesa:amber to simplify reverse dependencies of media-libs/mesa. Bug: https://bugs.gentoo.org/843440 Signed-off-by: Matt Turner <mattst88@gentoo.org> media-libs/mesa-amber/Manifest | 1 + .../mesa-amber-21.3.8.ebuild} | 5 ++++- media-libs/mesa-amber/metadata.xml | 18 ++++++++++++++++++ 3 files changed, 23 insertions(+), 1 deletion(-) Two questions, on behalf of everyone who's going to end up installing this: 1) Is USE=gallium gone for good, and why? i915g was working fine here until now... 2) Is there going to be a news item explaining how to use this? There's zero docs or pointers, and out of the box it does nothing (i.e. my laptop's now unusable until I find time to downgrade it to <media-libs/mesa-22). (In reply to Enne Eziarc from comment #3) > Two questions, on behalf of everyone who's going to end up installing this: > > 1) Is USE=gallium gone for good, and why? i915g was working fine here until > now... i915g is still in the main branch of mesa. You don't need mesa-amber for that. All of the drivers provided by mesa-amber are classic drivers, so there's no use in a gallium USE flag. > 2) Is there going to be a news item explaining how to use this? Hopefully. > There's zero > docs or pointers, and out of the box it does nothing (i.e. my laptop's now > unusable until I find time to downgrade it to <media-libs/mesa-22). I'm not sure why you think you need mesa-amber? (In reply to Matt Turner from comment #4) > I'm not sure why you think you need mesa-amber? ingrained paranoia and a lack of signs saying "keep out", I guess. PEBKAC. I updated to mesa-22, my old hardware's GPU (945GME) promptly stopped working, while looking for an answer I saw the VIDEO_CARDS="i915" flag was gone and this mesa-amber package now had it, (wrongly) believed this was where all the pre-opengl3 stuff lived now, and tried to install it with no success. Anyway I've now figured out what I needed was VIDEO_CARDS="intel" on mesa; that's the missing instruction I needed. It costs 5MB of extra drivers I'll never use, but whatever. There's the other issue remaining - mesa-amber installs drivers that don't get loaded automatically because they're not in the usual path, and it's not obvious how to coax it into working. No longer my problem but ati/nv users will probably hit it. Calling this done. |