[pacman-dev] _alpm_checkconflicts may add duplicated entries to baddeps
Hi! As I see, if there is a conflict in package list, then we may add this twice to the conflict list (because find that conflict twice). Anyway, I don't like this assymmetric "conflict" storing. Bye, ngaba ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/
We may use the (order == 0) information to recognize this special case. ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/
On Mon, Aug 13, 2007 at 03:06:00PM +0200, Nagy Gabor wrote:
Hi! As I see, if there is a conflict in package list, then we may add this twice to the conflict list (because find that conflict twice). Anyway, I don't like this assymmetric "conflict" storing.
Usually, if pkgA and pkgB are in conflict, it's either pkgA which conflicts with pkgB, or pkgB which conflicts with pkgA, not both, right? I'm not sure I like the current conflict storing either though.
2007/8/13, Xavier
On Mon, Aug 13, 2007 at 03:06:00PM +0200, Nagy Gabor wrote:
Hi! As I see, if there is a conflict in package list, then we may add this twice to the conflict list (because find that conflict twice). Anyway, I don't like this assymmetric "conflict" storing.
Usually, if pkgA and pkgB are in conflict, it's either pkgA which conflicts with pkgB, or pkgB which conflicts with pkgA, not both, right?
I'm not sure I like the current conflict storing either though.
If pkgB was introduced in some repo after pkgA was last modified, then conflicts in asymmetric usually, but AFAIR pkgA is fixed soon after this. (at least that's what I've observed for some extra and community packages). -- Roman Kyrylych (Роман Кирилич)
If pkgB was introduced in some repo after pkgA was last modified, then conflicts in asymmetric usually, but AFAIR pkgA is fixed soon after this. (at least that's what I've observed for some extra and community packages). Yes, but from the viewpoint of the package manager the only important information: pkgA conflicts with pkgB (== pkgB conflicts with pkgA). Bye, ngaba
---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/
participants (3)
-
Nagy Gabor
-
Roman Kyrylych
-
Xavier