Re:The FreeBSD Foundation Is Soliciting Project Proposals
by mapleoin on Saturday March 30, 2013 @04:10PM
(#5466514)
Just in case you (or anyone else) is wondering. You can find out which rpm installed a file with rpm -qf <file>. And you can see all the files in an installed rpm with rpm -ql <pkg>.
I'm also curious about the dpkg equivalent.
Re:The FreeBSD Foundation Is Soliciting Project Proposals
by sigil on Saturday March 30, 2013 @04:46PM
(#5466623)
> I'm also curious about the dpkg equivalent.
dpkg -S /path/to/file
Re:The FreeBSD Foundation Is Soliciting Project Proposals
by e12e on Saturday March 30, 2013 @05:29PM
(#5466723)
dpkg -L <package> lists files in a package.
edit: dpkg -l | --list lists packages, -L|--listfiles lists files in packages (which is why it isn't just dpkg -l)
Re:The FreeBSD Foundation Is Soliciting Project Proposals
by e12e on Saturday March 30, 2013 @05:28PM
(#5466720)
As already mentioned "dpkg -S file" will show which package installed which file. If you install apt-file, you can also search for which package, installed or not, contains a file:
$ apt-file search /etc/apache2/ports.conf
apache2.2-common: /etc/apache2/ports.conf
$ aptitude search apache2.2-common
p apache2.2-common - Apache HTTP Server common files
$ dpkg -S /etc/apache2/ports.conf
dpkg-query: no path found matching pattern
/etc/apache2/ports.conf
One benefit as well is that it seems to do less random io/spinlocking when doing stuff with the package database than the old tools, which means large install runs (compiled or not) go much faster.
It also builds in vulnerability auditing, which is also great. Previously this required a separate port.