Download several copies of packages for different environments if needed

[KarlOfDuty]

@grische in #42:

That seems like intended behaviour:

• Ansible 8.7.0 and earlier requires only '>=3.9' according to pypi and hence is considered compatible with all your envs.
• Ansible 9.0.1 (the one after 8.7.0) requires '>=3.10' which does not match your first few envs, so it is being dropped.
• Ansible 12.0.0 requires '>=3.11' which does not match many of your environments, so it is also being dropped.

There is another issue about a feature request to have an "matches either environment" and not "matches all environments", if that's what you're looking for: #21 (comment)

In the example above I would expect getting version 8.7.0 for my python 3.9 environment, 9.0.1 for my 3.10 environment, and 12.0.0 for my python 3.12 environment but I only get 8.7.0 as that is the only version that works for all. I am not downloading it as a dependency for a specific package, I want the latest version to be available in the air-gapped environment for each python version we have.

Could a flag be added for this?

[alex-orange-UofU]

I think this is a duplicate of my #21 issue. I agree that something should be done here. I don't know if there's a reason for a flag for it. Without doing this it straight up breaks, i.e. why not just change to download each version and not flag it.

[KarlOfDuty]

I agree this should be the default mode, but I can sort of see why someone would want the current implementation as well.

Some may not care about the versions of the packages and may instead value that every environment runs the exact same version for consistency. One could set the versions manually in the config in that case, but the current functionality would do that automatically for people. Not sure if there are any real users with this use case though.

And idk if I agree that this is a duplicate of your issue, this one is more about a specific feature request while yours is about a specific mirror problem you have, just like my previous issue. I think this makes it more clear what we want.

[alex-orange-UofU]

I think you're right that they're different in the sense that I realized after reading yours some more, that you want a feature, which apparently doesn't completely block you. It gave you a set of versions that technically worked. For me however I didn't even get a set of packages that worked for all environments, so it actually needed to take other action. That's where I'm saying I'm not sure that there's a way to go the 1-package for all route when certain packages won't work across all environments anyhow. (I do see what you say about same version package, but I think if someone's sensitive about package version they'd better be pinning the version or the first time the package maintainer puts out a new version that covers all of their environments they'll be in trouble).

[KarlOfDuty]

Yeah that's true, probably best to always download the latest version available for each environment then.