On Sat, 23 Mar 2024 16:34:28 +0100 Marcell Meszaros <marcell.meszaros@runbox.eu> wrote:
Marcell Meszaros <marcell.meszaros@runbox.eu> wrote:
Affected are 10 or so AUR packages, none of which have any viable use case in lib32 at all, and never even had.
Really? So you can guarantee that nobody could be using these libraries for any local project? It doesn't matter in the least that no AUR package depends on it.
Nobody pushed for getting fixes in this dependency chain for the last 2 years.
AV1 and HEIF etc formats were introduced a decade and a half after Microsoft forced practically all PC OEM's of the world to transition to x86_64. There are no native libraries and applications that need such in lib32.
And if a dependency chain for such a nonexistent use case is rotting for years on AUR, that's pretty much all the evidence one needs to prove total lack of demand.
Just because Arch repo's x86_64 multimedia library chain got slavisly recreated on AUR in lib32 without a thought whether there is any point at all, it doesn't mean these packages are legitimate and needed entities.
Basically these were pushed to AUR due to lack of understanding and due diligence in this matter.
I hope this clarifies my line of thinking.
Cheers, Marcell (MarsSeed)
Yes, your line of thinking is that if you're not aware of any usecase, it should be disallowed. Things don't work that way. I really don't know why you insist on picking fights with people, if they want to maintain it, that's up to them. If they're orphans, whatever, but just stop with all of the extra crap.