-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What version of ansible-base should ansible depend on? #94
Comments
Could you write down a few examples? Are you suggesting Also, s/ansible/ansible-base/, right? |
Yes, the second ansible should have been ansible-base. I've corrected the description now. Example of what we do now:
This should mean that whenever you upgrade the ansible package, the ansible-base package may be updated as well. Example of the alternative:
This scenario means that you can continue to run an older, compatible, version of ansible-base (anything i the 2.10.x series) with newer versions of this ansible release series. |
For pushing people to update ansible-base, the first scenario sounds better. But OTOH testing against pre-release combos may suffer. |
I think non-pre-releases of ansible should require at least the latest compatible ansible-base package available via PyPI which isn't a prerelease - i.e. what we are currently doing. If you want to try ansible with another ansible-base, you can always install that one manually and install ansible with Prerelease versions of ansible could have less strict requirements though IMO. |
The answer to this was: ansible 2.10.x should depend on ansible-base >= 2.10.y with latest y that was around when ansible 2.10.x is built: |
The current ansible package will depend on the latest version of ansible-base at the time the build file is built (around beta release of the next version of ansible) or any newer compatible version.
Is that what we want or do we want to always use X.Y.0 or newer?
The text was updated successfully, but these errors were encountered: