FS#12199 - pacman: --ignore should work recursive or give a warning
Attached to Project:
Pacman
Opened by Erwin Van de Velde (evdvelde) - Friday, 21 November 2008, 14:31 GMT
Last edited by Xavier (shining) - Friday, 17 July 2009, 22:10 GMT
Opened by Erwin Van de Velde (evdvelde) - Friday, 21 November 2008, 14:31 GMT
Last edited by Xavier (shining) - Friday, 17 July 2009, 22:10 GMT
|
Details
Description:
If I use the --ignore flag of pacman for e.g. kernel26 because I do not want / cannot reboot the host at the moment (servers etc.), I now get an error for e.g. the nvidia module that cannot be updated because of unsatisfied dependencies and I have to add it to --ignore and so on. In this case it is clear that the unsatisfied dependency is kernel26 I asked not to upgrade. In my opinion, nvidia should be ignored automatically together with the kernel26 package instead of demanding the user to list every package separately in the ignore list. A warning that the package is ignored to would suffice. |
This task depends upon
Closed by Xavier (shining)
Friday, 17 July 2009, 22:10 GMT
Reason for closing: Implemented
Additional comments about closing: should be implemented in 3.3.
reopen if not.
Friday, 17 July 2009, 22:10 GMT
Reason for closing: Implemented
Additional comments about closing: should be implemented in 3.3.
reopen if not.
1. Adding a new (satisfier) package to the target list. I.e. trying to accomplish user's wish.
2. Removing a package from the target list (which has unsatisfied dependency). Maybe, fall-back from 1.
(In case of removal, we have -Rc (~1.) and -Ru (~2.))
I can only support a general solution for 2. (like -Ru), not a recursive --ignore.
I like the current logic of --ignore, it simply hides some sync packages. And -Su is equivalent with -S <outdated_pkgs>, so the current behavior is correct imho. (However, I know that adding nvidia manually to IgnorePkg is not very comfortable.)
FS#9395?