FS#61838 - [pacman] Improve man for `--noconfirm` option + add more `--noconfirm` variations
Attached to Project:
Pacman
Opened by Ivan (dr.terrible) - Saturday, 23 February 2019, 09:29 GMT
Last edited by Allan McRae (Allan) - Saturday, 23 February 2019, 09:36 GMT
Opened by Ivan (dr.terrible) - Saturday, 23 February 2019, 09:29 GMT
Last edited by Allan McRae (Allan) - Saturday, 23 February 2019, 09:36 GMT
|
Details
Summary and Info:
For script use, pacman does provide the `--noconfirm` key that picks the default option in each prompt. However, this may not asways be desirable and to my knowledge there's no way to force "yes". I (and probably other users) would like something like `--noconfirm-yes` `--noconfirm-no` in addition to the `--noconfirm` switch that picks default action. Additionally, the documentation of the `--noconfirm` option could be improved by stating that it applies the default option for each prompt, right now it goes "Bypass any and all “Are you sure?” messages. It’s not a good idea to do this unless you want to run pacman from a script." which is a little uncertain on how it actually bypasses the prompts, e.g. for a user wondering what pacman actually does, say, in the `pacman -Scc --noconfirm` case. Scenario that brought me here: ------------------------------ Building docker image, slimming each installation layer by doing `pacman -Scc` after installations are done to keep pacman cache out of the history. When I do `pacman -Scc --noconfirm`, pacman does delete unused repos but doesn't clean the cache because the default option for that is "N" and there's no way to override that except employing a tool other than pacman (paccache or just rm). |
This task depends upon
Closed by Allan McRae (Allan)
Saturday, 23 February 2019, 09:36 GMT
Reason for closing: Won't implement
Additional comments about closing: yes | pacman -Scc
Saturday, 23 February 2019, 09:36 GMT
Reason for closing: Won't implement
Additional comments about closing: yes | pacman -Scc