Closed NICHOLAS85 closed 3 years ago
I've identified a difference in behavior from paru compared to yay. I'm going to close this until I've had time to check all implementations.
For now the only problematic difference I found was updating the package database. Paru expects a target package for reinstallation, I've simply hidden this error message. Some operations can be simplified with new flags however I found some of these flags haven't been implemented yet or aren't working correctly. For now I'll keep an eye on development and update as necessary.
Noting for future reference: Paru provides a remove orphans function via the -c/--clean
flag. Once a bugfix I'm tracking is included in a release I'll update user_interfaces
and implementation
Additionally, the update-package-database error message turned out to be a bug, i'll revert the change I made once the fix hits a release.
Fixes I've been tracking have been included in latest release meaning this PR is ready to be accepted
Looks good to me!
No changes from yay script were necessary besides yay -> paru rename.