Add sync044 pactest : A dependency induces a replacement.
That is the problem mentioned by Nagy there (with suggestions for fixing it) : http://www.archlinux.org/pipermail/pacman-dev/2007-August/009082.html
If a dependency conflicts with a local package and has to replace it, the PM_SYNC_TYPE_DEPEND information is lost, and the resulting install reason is wrong (the package is marked as explictly installed).
Signed-off-by: Chantry Xavier <shiningxc@gmail.com>
Well, this should be fixed with http://www.archlinux.org/pipermail/pacman-dev/2007-September/009271.html Please follow the thread, and let me know your -U and -S opinion (there are 2 different ways: the Vmiklos-way and the ~Arch-way). If I get enough feedback, I will implement your choice. My opinion: -%REASON% should show the _initial_ reason (which is computed after the _first_ install of the package), and later -S/-U will keep this reason (without examining that this is a pulled dependency, or listed in the target list by user) [this is the ~Arch way]: I prefer this, because [1.] if the user don't want to update his whole system with -Su (because he has low-bandwidth net for example), he can update a dependency (by doing "pacman -S dependency") without change its reason field to explicit; [2.] and unneeded dependency->explicit conversion may prevent pacman from orphan detection (can happen in Vmiklos-way) and missing dependency->explicit conversion just may list some extra orphan packages (can happen in ~Arch-way); [3.] explicit is the "final"/irreversible state of a package -IMHO we need an ability to change the reason fields in localdb /whatever you choose/, because users may want to mark/unmark their "important" packages (and pacman's automatism is unpredictable ;-) Bye, ngaba ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/