On Mon, Feb 10, 2020 at 05:48:42AM -0500, Sam Hartman wrote: > I'll note there's another case where this could be valuable. > If there is an installer in contrib, you can express dependencies on the > package being available in Debian. > Depending on how that installer works, you may not be able to express > dependencies on the installed version in Debian. >
I agree with this argument when you using the word "installer". We have a lot of installers in contrib. Though a package manager is another kind of "installer", but the situation is different. Says I'm a user of pip. I install a python library using pip, and pin it at version A. Now a package in contrib try to use pip to install this library with version B. This becomes conflict. If another package declares dependencies with this package, the version management becomes mess. So technically this doesn't work, only causing problem for end users.
