I'm absolutely new to packaging, so forgive me if I am asking something obvious for an experienced packager...
How can I be sure that mentioned all the dependencies correctly in my package?
Say that my application make use of lib
library-xyz which is not installed by default. If I build the package and install it on my developing machine,
library-xyz will be installed already, so - even if I failed to mention it as a dependency - the program will still run correctly. But another user on a fresh install of ubuntu won't have
library-xyz installed and the program will likely crash for him.
The way I am testing now is having a fresh ubuntu install running in a VM and installing the package there, but since it seems like a common problem, I wonder if there is a better way to test, something adopting the same philosophy of
chroot but that - instead of "cutting out" parts of the filesystem would "cut out" all those installed packages that are not "default" in a clean ubuntu installation.
I'm packaging python programs.