FS#72556 - [mesa-demos] Consider splitting package
Attached to Project:
Arch Linux
Opened by Ronan Pigott (Brocellous) - Wednesday, 27 October 2021, 09:07 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 27 November 2021, 17:11 GMT
Opened by Ronan Pigott (Brocellous) - Wednesday, 27 October 2021, 09:07 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 27 November 2021, 17:11 GMT
|
Details
Description: Consider splitting useful programs out of the
mesa-demos package.
I know it isn't really standard practice to split packages, but sometimes exceptions have been made and I think this is a good case. mesa-demos is an odd package. It has glxinfo, eglinfo, es2_info, and other *info's which are eminently useful programs. They are commonly used/requested in bug reporting, and they're a good first step in debugging and verification. glxinfo at least is referenced all over the wiki. But mesa-demos also contains literally _hundreds_ of next-to-worthless binaries that seriously pollute /usr/bin. glxgears and some of its *gears and friends might be useful demos, but passed that the number of commands from this package a user intentionally runs is probably very low. Emphasis on intentionally, because almost all of them have short names that will easily slip into your shell completions or dmenu_run selection. Finally, they all lie flat in /usr/bin so it's not simple to NoExtract them all. For that reason, I think a "mesa-utils" (like "libva-utils", provider of vainfo) or "mesa-tools" (like "vulkan-tools", provider of vulkaninfo) could be split from mesa-demos that has some select useful packages and leaves the junk. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Saturday, 27 November 2021, 17:11 GMT
Reason for closing: Implemented
Saturday, 27 November 2021, 17:11 GMT
Reason for closing: Implemented
So, +1 in favour of splitting, especially if Plasma 5.24 requires glxinfo.
https://packages.debian.org/bullseye/amd64/mesa-utils/filelist
https://packages.debian.org/bullseye/amd64/mesa-utils-extra/filelist
We definitely don't need 2 packages. I think a package with glxinfo and eglinfo would be fine, and glxgears maybe.