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.
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.
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
Opened by Francois Charette (Firmicus) - Friday, 03 March 2006, 21:43 GMT
Last edited by Xavier (shining) - Tuesday, 29 April 2008, 11:13 GMT
|
Details1). 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.) 
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.
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.
Or maybe there should be official arch-tools package that will contain scripts like this.
:D
Any objection to that?
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)
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
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