How to dentify what files or directories are modified when a debian package is installed? [duplicate]

Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
This question already has an answer here:
How can I list all files which have been installed by an APT package?
1 answer
If I do a sudo apt install example-package -y then the apt program will pull the deb file from its repo and install it in the system.
Some program will have conf files inside /etc folder and its executable file will be in /bin and some other file may or may not be in /usr/share/example-package folder.
Is there anyway to get the list of created files / folders that took place during such an installation?
files apt software-installation
marked as duplicate by muru, Kiwy, jimmij, Jeff Schaller, GAD3R Apr 29 at 16:15
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |Â
up vote
2
down vote
favorite
This question already has an answer here:
How can I list all files which have been installed by an APT package?
1 answer
If I do a sudo apt install example-package -y then the apt program will pull the deb file from its repo and install it in the system.
Some program will have conf files inside /etc folder and its executable file will be in /bin and some other file may or may not be in /usr/share/example-package folder.
Is there anyway to get the list of created files / folders that took place during such an installation?
files apt software-installation
marked as duplicate by muru, Kiwy, jimmij, Jeff Schaller, GAD3R Apr 29 at 16:15
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
Of course, maintainer scripts could additionally create or modify files, and it's in general not possible to always predict what the scripts will do.
â muru
Apr 29 at 7:11
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
This question already has an answer here:
How can I list all files which have been installed by an APT package?
1 answer
If I do a sudo apt install example-package -y then the apt program will pull the deb file from its repo and install it in the system.
Some program will have conf files inside /etc folder and its executable file will be in /bin and some other file may or may not be in /usr/share/example-package folder.
Is there anyway to get the list of created files / folders that took place during such an installation?
files apt software-installation
This question already has an answer here:
How can I list all files which have been installed by an APT package?
1 answer
If I do a sudo apt install example-package -y then the apt program will pull the deb file from its repo and install it in the system.
Some program will have conf files inside /etc folder and its executable file will be in /bin and some other file may or may not be in /usr/share/example-package folder.
Is there anyway to get the list of created files / folders that took place during such an installation?
This question already has an answer here:
How can I list all files which have been installed by an APT package?
1 answer
files apt software-installation
asked Apr 29 at 6:59
Vizkrig
132
132
marked as duplicate by muru, Kiwy, jimmij, Jeff Schaller, GAD3R Apr 29 at 16:15
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by muru, Kiwy, jimmij, Jeff Schaller, GAD3R Apr 29 at 16:15
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
Of course, maintainer scripts could additionally create or modify files, and it's in general not possible to always predict what the scripts will do.
â muru
Apr 29 at 7:11
add a comment |Â
Of course, maintainer scripts could additionally create or modify files, and it's in general not possible to always predict what the scripts will do.
â muru
Apr 29 at 7:11
Of course, maintainer scripts could additionally create or modify files, and it's in general not possible to always predict what the scripts will do.
â muru
Apr 29 at 7:11
Of course, maintainer scripts could additionally create or modify files, and it's in general not possible to always predict what the scripts will do.
â muru
Apr 29 at 7:11
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
accepted
Yes. From man dpkg:
-L, --listfiles package-name...
List files installed to your system from package-name.
Using your example, the command would be dpkg -L example-package.
add a comment |Â
up vote
2
down vote
If you want to check the contents before installing a package, you can also go to http://packages.debian.org/<package name> then select the version of the package you wish to inspect, and then at the bottom of the page there will be a table of download links for that package for each architecture available. On the right-most column of that table, there are links labeled [list of files]. Click on the link matching your system architecture, and you'll see exactly what the package contains without even downloading it.
If you have already downloaded a .deb package, but haven't installed it yet, you can view its contents with dpkg -c <package.deb>. If you want to see what the package's post-install script would do, you can use dpkg -I <package.deb> postinst. Instead of postinst, you can also use keywords preinst, postrm and prerm to view the respective scripts, if they exist in the package.
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Yes. From man dpkg:
-L, --listfiles package-name...
List files installed to your system from package-name.
Using your example, the command would be dpkg -L example-package.
add a comment |Â
up vote
2
down vote
accepted
Yes. From man dpkg:
-L, --listfiles package-name...
List files installed to your system from package-name.
Using your example, the command would be dpkg -L example-package.
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Yes. From man dpkg:
-L, --listfiles package-name...
List files installed to your system from package-name.
Using your example, the command would be dpkg -L example-package.
Yes. From man dpkg:
-L, --listfiles package-name...
List files installed to your system from package-name.
Using your example, the command would be dpkg -L example-package.
answered Apr 29 at 7:02
dsstorefile1
1,516212
1,516212
add a comment |Â
add a comment |Â
up vote
2
down vote
If you want to check the contents before installing a package, you can also go to http://packages.debian.org/<package name> then select the version of the package you wish to inspect, and then at the bottom of the page there will be a table of download links for that package for each architecture available. On the right-most column of that table, there are links labeled [list of files]. Click on the link matching your system architecture, and you'll see exactly what the package contains without even downloading it.
If you have already downloaded a .deb package, but haven't installed it yet, you can view its contents with dpkg -c <package.deb>. If you want to see what the package's post-install script would do, you can use dpkg -I <package.deb> postinst. Instead of postinst, you can also use keywords preinst, postrm and prerm to view the respective scripts, if they exist in the package.
add a comment |Â
up vote
2
down vote
If you want to check the contents before installing a package, you can also go to http://packages.debian.org/<package name> then select the version of the package you wish to inspect, and then at the bottom of the page there will be a table of download links for that package for each architecture available. On the right-most column of that table, there are links labeled [list of files]. Click on the link matching your system architecture, and you'll see exactly what the package contains without even downloading it.
If you have already downloaded a .deb package, but haven't installed it yet, you can view its contents with dpkg -c <package.deb>. If you want to see what the package's post-install script would do, you can use dpkg -I <package.deb> postinst. Instead of postinst, you can also use keywords preinst, postrm and prerm to view the respective scripts, if they exist in the package.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
If you want to check the contents before installing a package, you can also go to http://packages.debian.org/<package name> then select the version of the package you wish to inspect, and then at the bottom of the page there will be a table of download links for that package for each architecture available. On the right-most column of that table, there are links labeled [list of files]. Click on the link matching your system architecture, and you'll see exactly what the package contains without even downloading it.
If you have already downloaded a .deb package, but haven't installed it yet, you can view its contents with dpkg -c <package.deb>. If you want to see what the package's post-install script would do, you can use dpkg -I <package.deb> postinst. Instead of postinst, you can also use keywords preinst, postrm and prerm to view the respective scripts, if they exist in the package.
If you want to check the contents before installing a package, you can also go to http://packages.debian.org/<package name> then select the version of the package you wish to inspect, and then at the bottom of the page there will be a table of download links for that package for each architecture available. On the right-most column of that table, there are links labeled [list of files]. Click on the link matching your system architecture, and you'll see exactly what the package contains without even downloading it.
If you have already downloaded a .deb package, but haven't installed it yet, you can view its contents with dpkg -c <package.deb>. If you want to see what the package's post-install script would do, you can use dpkg -I <package.deb> postinst. Instead of postinst, you can also use keywords preinst, postrm and prerm to view the respective scripts, if they exist in the package.
answered Apr 29 at 10:25
telcoM
10.2k11032
10.2k11032
add a comment |Â
add a comment |Â
Of course, maintainer scripts could additionally create or modify files, and it's in general not possible to always predict what the scripts will do.
â muru
Apr 29 at 7:11