Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#68882 - [primus] make it a simple wrapper
Attached to Project:
Community Packages
Opened by Emil (xexaxo) - Monday, 07 December 2020, 17:20 GMT
Last edited by Morten Linderud (Foxboron) - Saturday, 19 December 2020, 10:42 GMT
Opened by Emil (xexaxo) - Monday, 07 December 2020, 17:20 GMT
Last edited by Morten Linderud (Foxboron) - Saturday, 19 December 2020, 10:42 GMT
|
DetailsDescription:
As mentioned in my recent email [1], as-is the package duplicates causing serious issues with GLVND enabled systems. In particular - Arch has been fully GLVND since 23 Nov 2019, when the final piece (server-side GLVND for xorg) xorg-xserver v1.20.6 was released. Here is how I've addresses the issue [2]. NOTES: - bumblebee changes will be reported separately - reverse PRIME is untested - don't have physical access to my test machine - legacy nvidia drivers (pre 390.x) that live in AUR can carry an "legacy" version of this package. Afaict such drivers are not to be supported by official Arch packages. [1] https://lists.archlinux.org/pipermail/arch-general/2020-December/048411.html [2] https://github.com/evelikov/primus |
This task depends upon
This way it's obvious a) what it actually is and b) removes any ambiguity wrt the official project.
Can do some extra patches, considering there's interest in the topic.
Similar to the BB side, I think we can effectively consider upstream dead and move on with the transitional package proposed. Right?