diff options
| author | Chantry Xavier <shiningxc@gmail.com> | 2008-01-28 19:49:27 +0100 |
|---|---|---|
| committer | Dan McGee <dan@archlinux.org> | 2008-05-13 15:49:02 -0500 |
| commit | d5278ebb3ba94efdc9fffb7924ac66b6747d9011 (patch) | |
| tree | d83bd99db2b5d93d8b8398c393745b1032159db3 /pactest/tests/upgrade059.py | |
| parent | f43805d875ad5c672afbbfff48bded2087204773 (diff) | |
| download | pacman-d5278ebb3ba94efdc9fffb7924ac66b6747d9011.tar.xz | |
Add SyncFirst option.
This patch offers a way to fix FS#9228.
By putting "SyncFirst = pacman" in pacman.conf, the version check will
happen before the transaction really starts, and before any replacements is
made.
Otherwise, no version check is done.
The sync301 pactest was updated to use this SyncFirst option.
Example session with SyncFirst = pacman, and a newer pacman version
available :
$ pacman -Su (or pacman -S <any targets>)
:: the following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n]
resolving dependencies...
looking for inter-conflicts...
Targets: pacman-x.y.z-t
Total Download Size: x.xx MB
Total Installed Size: x.xx MB
Proceed with installation? [Y/n] n
As Nagy previously noted, doing this check on any -S operations might look
intrusive, but it can be required.
For example, the case where you want to install a package with versioned
provisions, using a pacman version which didn't support that feature yet
(and there is already a newer pacman in sync db supporting it).
Signed-off-by: Chantry Xavier <shiningxc@gmail.com>
Signed-off-by: Dan McGee <dan@archlinux.org>
Diffstat (limited to 'pactest/tests/upgrade059.py')
0 files changed, 0 insertions, 0 deletions