Re: [pacman-dev] [PATCH] Do not remove conflict by default

2009-08-31 Thread Xavier
On Mon, Aug 31, 2009 at 4:50 AM, Allan McRaeal...@archlinux.org wrote: Imho your noyes default behavior is better... Moreover, maybe we should also print somehow the conflict itself in warning, because 'udev conflicts with initscripts2009.07' (btw, why is there 2 conflicts line udev's

[pacman-dev] [PATCH] Do not remove conflict by default

2009-08-31 Thread Nagy Gabor
From 66cb7b5d48ae173944531318022d351f4e503172 Mon Sep 17 00:00:00 2001 From: Nagy Gabor ng...@bibl.u-szeged.hu Date: Mon, 31 Aug 2009 23:54:51 +0200 Subject: [PATCH] Do not remove conflict by default When a conflict is detected, pacman asks if the user wants to remove the conflicting package. In

[pacman-dev] [PATCH] Do not remove conflict by default

2009-08-30 Thread Allan McRae
When a conflict is detected, pacman asks if the user wants to remove the conflicting package. In many cases this is a bad idea. e.g. udev conflicts with initscripts. Remove initscripts [Y/n] util-linux-ng conflicts with e2fsprogs. Remove e2fsprogs? [Y/n] This changes the query to [y/N].

Re: [pacman-dev] [PATCH] Do not remove conflict by default

2009-08-30 Thread Nagy Gabor
When a conflict is detected, pacman asks if the user wants to remove the conflicting package. In many cases this is a bad idea. e.g. udev conflicts with initscripts. Remove initscripts [Y/n] util-linux-ng conflicts with e2fsprogs. Remove e2fsprogs? [Y/n] This changes the query to [y/N].

Re: [pacman-dev] [PATCH] Do not remove conflict by default

2009-08-30 Thread Allan McRae
Nagy Gabor wrote: When a conflict is detected, pacman asks if the user wants to remove the conflicting package. In many cases this is a bad idea. e.g. udev conflicts with initscripts. Remove initscripts [Y/n] util-linux-ng conflicts with e2fsprogs. Remove e2fsprogs? [Y/n] This changes the