Enhancement suggestion for dependency script/module versioning

[wooseung-sim]

Expected Behavior

If required module has maximum version condition due to broken backward compatibility, install-script/module should guarantee any higher version than given condition should not be installed.
And if another dependency requires a higher version than previous max version condition, publish-script/module and/or install-script/module should report version conflicts on dependencies.

Current Behavior

version tag for nuget package for publishing uses 'Minimum version, inclusive' version notation only.
So, it cannot detect any dependency version confliction.

Possible Solution

If PowershellGet uses Min/Max version conditions not only when it finds script/module from the repository, but also when it generate nuget tags to publish, version conflicts can be detected at least installation time.

Context

As Powershell get cannot detect any version confliction on dependencies, we are managing and checking it manually whenever there are any updates on our powershell modules/scripts.

[Jaykul]

This is WRONG.

Install-Script and Install-Module must guarantee that at least one version that is less-than or equal to the expected maximum version is installed. They must not care if newer versions are also installed.

PowerShell (at Import-Module time) must make sure to import the right version. Having multiple versions available is not a conflict, and should not cause any warnings or problems at install.

This is implicit in the understanding of Side-by-side module installs.

And yes, it's possible that this may cause problems if two different modules requiring different versions of a third module are used by a single script (or a fourth module), but that's an acceptable risk. Blocking the install is not the answer.

[wooseung-sim]

I think my issue description is not good enough and didn't cover what I mean well.

I meant last case on previous comment. You said it's acceptable, but it was not really acceptable for me when it really happened.

Let's assume that module A has dependency on Dumb and Dumber modules. And Dumb and Dumber has dependency on same module Dumbest which does not have backward compatibility. And unfortunately Dumb and Dumber's dependency version definitions are conflict.

In this case, PowershellGet doesn't report any error or warning to author and user of module A.

If there were confliction while creating Module A, it is author's responsibility. But confliction can comes later by updates of Dumb and Dumber, if Module A doesn't have required version or max version restriction on dependencies.

So it would be better to have fair enough warning or error if there are conflictions among dependency modules to install, and it would be nice to have feature.