From 42042723a884930caf80ed578fc9fee2e0822bfb Mon Sep 17 00:00:00 2001 From: Dan McGee Date: Sun, 4 Oct 2009 09:48:56 -0500 Subject: doc: ensure SyncFirst behavior with flags is clear When a SyncFirst transaction kicks in, no flags like '--force' are honored. This is for good reason, as honoring something like '--asdeps' could be quite unintentional. Document this fact and a possible workaround. Signed-off-by: Dan McGee --- doc/pacman.conf.5.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'doc/pacman.conf.5.txt') diff --git a/doc/pacman.conf.5.txt b/doc/pacman.conf.5.txt index a1c1f2a6..3e361102 100644 --- a/doc/pacman.conf.5.txt +++ b/doc/pacman.conf.5.txt @@ -86,8 +86,11 @@ Options *SyncFirst =* package ...:: Instructs pacman to check for newer version of these packages before any sync operation. The user will have the choice to either cancel the current - operation and upgrade these packages first or go on with the current operation. - This option is typically used with the 'pacman' package. + operation and upgrade these packages first or go on with the current + operation. This option is typically used with the 'pacman' package. + *NOTE*: when a `SyncFirst` transaction takes place, no command line flags + (e.g. '\--force') are honored. If this is not ideal, disabling `SyncFirst` + and performing a manual sync of the involved packages may be required. *IgnoreGroup =* group ...:: Instructs pacman to ignore any upgrades for all packages in this -- cgit v1.2.3-70-g09d2