Control: severity -1 wishlist Control: tag -1 moreinfo On Sat, 2026-03-21 at 09:42:05 -0300, Tomas wrote: > package: dpkg
> #The issue: > > User wants to know what files were installed by running > 'apt install <package>' I don't think this is a clear enough use case, because this could be an interest in only the packages that actually got installed anew, and not any already installed dependencies that the system already had. What about alternative dependencies (as in "foo | bar")? What about dependencies satisfied by virtual packages provided by multiple real packages, etc. What about packages which are only Recommended but apt might install depending on how it is configured? What about the matching query on package removals? (Which dpkg would be unable to answer as it would no longer have the list of removed files.) > He can run 'dpkg -L <package>' but that only shows files installed > by the metapackage itself, not its dependencies. TBH, it does not seem like this request belongs in dpkg itself, as it does not have enough information to properly answer the question that is supposedly being asked, as mentioned above, because that depends on the previous dpkg state and how a frontend like apt is configured. > He can also use 'apt-cache depends --recurse', but that produces huge > files with too much info, not just the files added. To get only the list of Depends and Pre-depends one can use «apt-cache depends --important --recurse», but apt by default will install Recommends, so that will depend on how it is configured. Given the above, I'm inclined to close this as a wontfix. Thanks, Guillem
