spystath
Joined 15 years ago
Joined 15 years ago
I think we are well past (1) but (2) could be mitigated by tighter controls on AUR accounts and potentially additional safeguards from AUR helpers. Maybe show a big scary warning if the package has changed owners recently. I know there will still be people that will "y" their way forward but it's better than nothing.
Or just avoid AUR helpers altogether and inspect/build the packages you need yourself from their PKGBUILDs directly.
Nothing about Android is open except the absolutely minimum amount of linux kernel that's required to boot the thing. Then it's blobs and restrictions all the way to the screen.
That being said, I'm not against removing features but neither this or the original post provide any substantial rationale on why it should be removed. Uses for XSLT do exist and the alternative is "just polyfill it" which is awkward especially for legacy content.
I'm afraid (2) will probably never work properly :-(
[0] https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317
[1] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...
[2] https://github.com/NVIDIA/egl-wayland/pull/104#issuecomment-...