Affected Version paru 2.1.0 and older Description Pacman v7.1.0 and libalpm v16.0.0 got released in arch-testing as of today. The new version of libalpm break paru (as intended), and as of now paru...
Loooolll! I love them raising a stink about forking I’m another language. Go for it! Nobody cares and I’m sure it’ll reach feature parity by the time paru is updated. 🙄 And then mentioning Lunduke saying something negative about Rust. Isn’t he some wacko conspiracy/Linux YouTuber? That all made for a good laugh.
Anyway, I really like Paru, but I’ve switched back to yay until they get a fix. Really not a big deal.
The best part is that it shows that they don’t have a clue. If you are “forking” a project to change it language is not a fork is a rewrite. It would be one thing if they were adding rust to an already existing project, but as far as I can tell the project is full rust from the beginning.
But they can’t say “I’m going to rewrite this in that other language” because that’s the thing they hate about rust, so if they said that it would be too obvious that they’re full of shit.
Loooolll! I love them raising a stink about forking I’m another language. Go for it! Nobody cares and I’m sure it’ll reach feature parity by the time paru is updated. 🙄 And then mentioning Lunduke saying something negative about Rust. Isn’t he some wacko conspiracy/Linux YouTuber? That all made for a good laugh.
Anyway, I really like Paru, but I’ve switched back to yay until they get a fix. Really not a big deal.
The best part is that it shows that they don’t have a clue. If you are “forking” a project to change it language is not a fork is a rewrite. It would be one thing if they were adding rust to an already existing project, but as far as I can tell the project is full rust from the beginning.
But they can’t say “I’m going to rewrite this in that other language” because that’s the thing they hate about rust, so if they said that it would be too obvious that they’re full of shit.