You are not logged in.
Among all the Pacman operations -T still remains a mystery to me. According to man page, it is supposed to list all the unsatisfied dependencies of a package but it does not work at all (for me). Commands like "pacman -T vlc" either print nothing or just print the name of the provided package; no matter the dependencies installed or not. Would somebody help me about the usage of this operation?
Last edited by newdave (2011-08-17 17:42:53)
Offline
I even don't know how to create such a conflict without manually screwing with the database. Pacman does not allow me to install a package without it's deps (at least there's nothing in the man page). Are you sure you have unmet dependencies?
Offline
'pacman -Rdd foo' will let you remove package foo even if it's a dependency for another package.
Offline
I even don't know how to create such a conflict without manually screwing with the database. Pacman does not allow me to install a package without it's deps (at least there's nothing in the man page). Are you sure you have unmet dependencies?
I was testing this feature on an uninstall package (vlc). So some of the dependencies are definitely not installed. I just want to know the function of Pacman -T.
'pacman -Rdd foo' will let you remove package foo even if it's a dependency for another package.
I don't want to remove anything.
Last edited by newdave (2011-08-17 16:30:14)
Offline
You've got the usage backwards. You specify dependencies that you suspect might be missing, and pacman checks against the database, printing any dependency that isn't met.
$ pacman -T 'notalib>=1.0' 'bash' 'notaprog' 'linux<3.0'
notalib>=1.0
notaprog
linux<3.0makepkg (and probably pacman) would cease to function if this was broken. It's bread and butter functionality for dependency resolution in alpm.
Last edited by falconindy (2011-08-17 17:59:10)
Offline
You've got the usage backwards. You specify dependencies that you suspect might be missing, and pacman checks against the database, printing any dependency that isn't met.
$ pacman -T 'notalib>=1.0' 'bash' 'notaprog' 'linux<3.0' notalib>=1.0 notaprog linux<3.0makepkg (and probably pacman) would cease to function if this was broken. It's bread and butter functionality for dependency resolution in pacman.
I see. Thanks.
Offline