FS#39514 - Same exit status whether pacman -Qdqt finds anything or not?
Attached to Project:
Pacman
Opened by Kevin (palintropos) - Tuesday, 18 March 2014, 04:10 GMT
Last edited by Allan McRae (Allan) - Tuesday, 18 March 2014, 04:12 GMT
Opened by Kevin (palintropos) - Tuesday, 18 March 2014, 04:10 GMT
Last edited by Allan McRae (Allan) - Tuesday, 18 March 2014, 04:12 GMT
|
Details
Summary and Info:
Why does `pacman -Qdqt` exit with status 1 whether it finds anything or not? I would expect it to exit with status 1 if it found anything, 0 otherwise, although I could see the other implementation making sense as well (since arguably it is a search algorithm and finding nothing is an error). However, returning 1 in both cases makes no sense to me. As an additional benefit, if this returned distinct codes, the following convenient action would be possible: pacman -Qdqt && pacman -Qdqt | pacman -Rns - or pacman -Qdqt || pacman -Qdqt | pacman -Rns - Both of these are more convenient at the command line and more readable in Bash scripts than the if...fi construct required to achieve the same effect now. Steps to Reproduce: With unneeded packages: $ yaourt -Qdqt gendesk lib32-libao lib32-sdl nasm subversion $ echo $? 1 Without: $ yaourt -Qdqt $ echo $? 1 |
This task depends upon
Closed by Allan McRae (Allan)
Tuesday, 18 March 2014, 04:12 GMT
Reason for closing: Not a bug
Additional comments about closing: pacman is not yaourt...
Tuesday, 18 March 2014, 04:12 GMT
Reason for closing: Not a bug
Additional comments about closing: pacman is not yaourt...