I was thinking about SyncFirst today and decided we need a good summary
of what the issues are and why the current and old implementations fail.
Why the current (pacman-4.0) implementation fails:
When a package in SyncFirst is to be updated, pacman will update that
first and pull everything in
This has outlived its usefulness and causes more problems than it
solves.
Signed-off-by: Dan McGee d...@archlinux.org
---
This is an RFC first of all, so please feel free to comment.
Pros:
1. Removes complexity and a fair amount of code.
2. Removes the hack necesary for download-only and print
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project The official pacman repository.
The branch, maint has been updated
via ca4142714137b16feabac09c4cda86b0a75036f8 (commit)
via
Add LocalFileSigLevel and RemoteFileSigLevel to control the signature
checking for pacman -U file and pacman -U url operations
respectively. Both values take the default of Optional TrustedOnly.
Signed-off-by: Allan McRae al...@archlinux.org
---
I would like to have the default level being what
