You are not logged in.
Hi,
Is there a way to ask pacman why a package was autoinstalled? (i.e. as a dependency of which package)
Thanks,
Antony
Offline
The Pacman Rosetta on the wiki has the most comprehensive list of pacman's commands and their correlates in the other package manages.
You can use the query option with the info switch (-Qi) to print information about an installed package. See man pacman for the details.
Offline
If a package was installed as a dependency, you can run this command to see which packages require it:
pacman -Qi packagename | grep RequiredIt may not help if its required by multiple packages, but its a start.
Offline
pacman -Qii packagename
shows all installed packages depending on packagename.
Offline
pacman -Qii packagename
shows all installed packages depending on packagename.
I fail to see the benefits of '-Qii' over what the previous posters suggested. Backup Files don't matter much here.
Offline
The Pacman Rosetta on the wiki has the most comprehensive list of pacman's commands and their correlates in the other package manages.
This is a GREAT article, thanks for posting.
Offline
jasonwryan wrote:The Pacman Rosetta on the wiki has the most comprehensive list of pacman's commands and their correlates in the other package manages.
This is a GREAT article, thanks for posting.
C'mon, the wiki has only a couple thousand articles, shame on you if you haven't glanced them over already ;-)
You may also like a more general summary http://distrowatch.com/dwres.php?resour … management
Offline
There's also pactree (included with pacman), which will show recursive dependencies of a package.
[rant]
This really ought to be mentioned somewhere. The only wiki article containing any reference is namcap, which I doubt non-dev users will read.
And I don't think most people will issue `pacman -Ql pacman` just to find the binary and other tools that the pacman package contains. Yes, most of them are more like dev-tools, but why shouldn't the users be aware of what great tools there are in the one of the most important package of the whole distro???
C'mon devs, at least mention it in the man pages of pacman or something.
[/rant]
Ok, what would be an appropriate way to document this on the wiki?
a)since makepkg is included in the package, I'd make a separate page for pactree
b) just mention it on the pacman wiki article
Last edited by smartass (2011-07-21 15:04:42)
KISS my Arch, Willy Gates!
Offline
falconindy wrote:There's also pactree (included with pacman), which will show recursive dependencies of a package.
[rant]
This really ought to be mentioned somewhere. The only wiki article containing any reference is namcap, which I doubt non-dev users will read.
And I don't think most people will issue `pacman -Ql pacman` just to find the binary and other tools that the pacman package contains. Yes, most of them are more like dev-tools, but why shouldn't the users be aware of what great tools there are in the one of the most important package of the whole distro???C'mon devs, at least mention it in the man pages of pacman or something.
[/rant]Ok, what would be an appropriate way to document this on the wiki?
a)since makepkg is included in the package, I'd make a separate page for pactree
b) just mention it on the pacman wiki article
The whole http://www.archlinux.org/packages/commu … n-contrib/ package is cool, e.g. bacman deserves a mention too.
Offline
schuay wrote:pacman -Qii packagename
shows all installed packages depending on packagename.
I fail to see the benefits of '-Qii' over what the previous posters suggested. Backup Files don't matter much here.
Oops, you're right. The way I remembered it, you needed to pass -i twice to see the Required By line, but that's obviously not correct.
Offline
Ok, what would be an appropriate way to document this on the wiki?
a)since makepkg is included in the package, I'd make a separate page for pactree
b) just mention it on the pacman wiki article
Even if you make a separate page you'd need to link it in the pacman article or it'd not really serve a purpose.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
There is also this:
expac -Q %N whateverpackageyouwanttocheckHandy for scripts and such.
Last edited by Mr.Elendig (2011-07-23 13:56:58)
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
karol wrote:schuay wrote:pacman -Qii packagename
shows all installed packages depending on packagename.
I fail to see the benefits of '-Qii' over what the previous posters suggested. Backup Files don't matter much here.
Oops, you're right. The way I remembered it, you needed to pass -i twice to see the Required By line, but that's obviously not correct.
You were thinking about -Si and -Sii most likely.
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline