FS#4099 - pacman -Ss and -Qs at once

Attached to Project: Pacman
Opened by Francois Charette (Firmicus) - Friday, 03 March 2006, 21:43 GMT
Last edited by Xavier (shining) - Tuesday, 29 April 2008, 11:13 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.0.5
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

1). When running "pacman -Ss foo" I would like to see in the output which packages
are actually installed on my system.
I have written a quick and dirty bash script to achieve this -- see attachment.

2). Also I would appreciate search options to further limit the search to package
names only (e.g. with pacman -Ssn foo) OR descriptions only (e.g. pacman -Ssd foo).

(Example illustrating both features: to check all available perl modules in the
repos one would run
pacman -Ssn ^perl-
and the installed packages would be flagged in some way in the output.)

(application/octet-stream)    pacsearch (0.8 KiB)
This task depends upon

Closed by  Xavier (shining)
Tuesday, 29 April 2008, 11:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  A different pacsearch tool is now included in pacman-contrib from community, and does -Ss and -Qs at once, with colorized output.
Comment by Roman Kyrylych (Romashka) - Saturday, 04 March 2006, 12:53 GMT
It would be nice to have these features in pacman.
Or maybe there should be official arch-tools package that will contain scripts like this.
Comment by Roman Kyrylych (Romashka) - Saturday, 07 April 2007, 16:36 GMT
pacsearch is in CVS now (in contrib directory).
Comment by Stefan O. (hybrid) - Saturday, 28 July 2007, 09:26 GMT
I wish I could vote for this feature request. I still don't see it in pacman 3.5.1
Comment by Stefan O. (hybrid) - Saturday, 28 July 2007, 15:28 GMT
Uhm, I don't see a edit or delete comment button anywhere. I meant pacman 3.0.5-2.
:D
Comment by Aaron Griffin (phrakture) - Friday, 03 August 2007, 20:03 GMT
It's in the contrib directory, which we don't actually distribute with the pacman package itself. Which is a shame, almost - perhaps we should push the contrib dir to /usr/share/pacman/ in the pacman package?
Any objection to that?
Comment by Roman Kyrylych (Romashka) - Saturday, 04 August 2007, 09:08 GMT
+10 for providing contrib/ contents in pacman package.
However, I think just putting them in /usr/share/pacman is not very useful.
I suggest:
/etc/bash_completion.d/pacman
/usr/share/zsh/site-functions/pacman
/usr/bin/{pacdiff,pacsearch,re-pacman,wget-xdelta.sh} (I think there could be more useful scripts added here)
/usr/share/pacman/{PKGBUILD,install}.proto (yeah, I know they are downloaded by abs, but users should not be required to run abs just to get them)
+ vim files (I don't know where they should be)
Comment by Aaron Griffin (phrakture) - Saturday, 04 August 2007, 17:25 GMT
I'm just a tad leery about moving EVERYTHING to /usr/bin by default

In addition, we should rename wget-xdelta if we move it to /usr/bin, just for tab complete purposes - the name tells use very little, but it _is_ pacman specific
Comment by Xavier (shining) - Wednesday, 20 February 2008, 18:37 GMT
bash and zsh completion are included now, as well as PKGBUILD and install protos in /usr/share/pacman/.
So we are left with the script and vim files.

A pacman-contrib community package was suggested for these :
http://www.archlinux.org/pipermail/pacman-dev/2008-February/011076.html
Comment by Allan McRae (Allan) - Tuesday, 29 April 2008, 10:10 GMT
Well, I made the pacman-contrib package and put it in [community] so can we close this now?

Loading...