-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add track_features to make ogre 1.10 the default #29
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2021.10.22.20.56.07
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2021.10.22.20.56.07
@conda-forge-admin, please rerender |
…nda-forge-pinning 2021.10.22.20.56.07
As it seems to be hard to fix the ogre 1.12 problems (see conda-forge/libignition-gazebo-feedstock#6 and gazebosim/gazebo-classic#2700), let's make ogre 1.10 the default from the time being. I copied exactly the same strategy used in gazebo.
In theory it should not be necessary to do the same in ign-sensors and ign-gui, but if we need we will do it.
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)