Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#15383 - [vercmp] Add a flag to use return code instead of printing result

Attached to Project: Pacman
Opened by Gavin Bisesi (Daenyth) - Sunday, 05 July 2009, 15:31 GMT
Last edited by Dan McGee (toofishes) - Sunday, 05 July 2009, 23:49 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Low
Reported Version 3.2.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

It would make it easier to script with vercmp if you could use the return code instead of having to compare the printed result. Maybe something like vercmp -r?
This task depends upon

Closed by  Dan McGee (toofishes)
Sunday, 05 July 2009, 23:49 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Closing by request, and although it could be handy it is easy to work around.
Comment by Dan McGee (toofishes) - Sunday, 05 July 2009, 23:31 GMT
I'm not quite sure how a negative number returned by vercmp is going to be translated into a return code.

In addition, can you give an example use case where the return code is necessary instead of a printed value? "$(vercmp 2 3)" is fairly straightforward to use in scripts.
Comment by Gavin Bisesi (Daenyth) - Sunday, 05 July 2009, 23:39 GMT
It's not necessary in any case, but it does make using it in "if" blocks a little ugly. I'm fine with a "won't implement".

Loading...