Prepare for 2.3.2

[mjcarroll]

Checklist

• Used a personal fork of the feedstock to propose changes
• [] Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

I have upstream-ed several of these patches. Once the 2.3.2 tag is added, this should be just about ready to go.

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

[mjcarroll]

@conda-forge-admin, please rerender

[traversaro]

Cool! Feel free to add yourself as a mantainer if you like!

[traversaro]

Regarding the test failures, I am afraid not all patches are backport that can be removed. I wanted to eventually contribute them upstream, but it was not super clear to me how OGRECave/ogre-next#232 and OGRECave/ogre-next#259 was going, so I decided to do it later (i.e. I forgot to do it, sorry!). Some related (hidden) comments can be found in conda-forge/staged-recipes#19384 .

[traversaro]

Looking a bit in the failures, one problem is that upstream Ogre-Next still does not install .pc files on Windows.

[mjcarroll]

One problem is that upstream Ogre-Next still does not install .pc files on Windows.

Yep, I have another local patch for it. Keeping this draft until we can get it all sorted/ported.

[mjcarroll]

I dumped patches from here, which I think will be slightly easier to maintain: https://github.com/gazebo-forks/ogre-next/tree/gazebo/v2-3

[talregev]

Any news?

[traversaro]

There is no 2.3.2 release for ogre-next .

[talregev]

What version is the next release?

[traversaro]

The latest is 2.3.1 and is packaged in conda-forge (see https://github.com/OGRECave/ogre-next/releases), the next one is 2.3.2 or some other version number > 2.3.1, probably ogre-next mantainers will decide that.

[talregev]

You mean when ogre-next will be releasing this PR will become relevant?
I thought they want to change something before the release.

Thank you for your details answer.

[traversaro]

You mean when it will be releasing on orge-next side this PR will become relevant?

Yes, this PR is just a preparation for the next release of ogre-next.

I thought they want to change something before the release.

Yes, it is possible more modifications will be necessary, that is why the PR is in draft.

[mjcarroll]

Replaced by #18