pacman - Archlinux32 fork of pacman

Age	Commit message (Collapse)	Author
2009-09-08	Change Y/n to y/N with REMOVE_PKGS (remove_unresolvable) callback	Nagy Gabor
	The main reason for this change is that scripts could not catch the removed targets with -S --noconfirm (the return value was 0). So the effect of a pacman command may have differed from the expected one. Moreover, for my taste the default no answer is better (I wanted to install the specified targets, not a subset of them). I had to change some pactest files as well, because now the default behavior is not to remove unresolvable targets. In fact, the only pactest file that tested this feature was ignore005.py. Signed-off-by: Nagy Gabor <ngaba@bibl.u-szeged.hu> Signed-off-by: Dan McGee <dan@archlinux.org>
2009-02-23	Enabled new interactive prompt and updated some tests	Bryan Ischo
	Enabled a new prompt to ask the user if they'd like to remove unresolvable packages from the transaction rather than failing it. Many pactest tests that used to fail now return success codes, because pacman now issues a prompt allowing the user to cancel rather than failing many transactions, and the pactest scripts always choose to cancel with no error rather than failing. The only net effect is that the return status of pacman is now 0 in cases where it used to be nonzero. Signed-off-by: Bryan Ischo <bryan@ischo.com> Signed-off-by: Dan McGee <dan@archlinux.org>
2008-07-07	Remove requiredby from pactests	Nagy Gabor
	Also remove some meaningless pactests (broken requiredby, requiredby*.py tests). requiredby001.py was renamed to upgrade076.py. Signed-off-by: Nagy Gabor <ngaba@bibl.u-szeged.hu> Signed-off-by: Dan McGee <dan@archlinux.org>
2007-06-04	Add five new pactest tests where pacman currently fails	Nagy Gabor
	Most of these new tests deal with provisions upon sync or upgrade being changed by packages, and pacman not being smart enough to deal with it yet. Signed-off-by: Dan McGee <dan@archlinux.org>