Add PR 437 to fix https://github.com/RoboStack/ros-humble/issues/33

[Tobias-Fischer]

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.

See RoboStack/ros-humble#33:

RuntimeError: copy_symlink: The file or directory is not a reparse point.: 
"C:\Users\runneradmin\conda_pkgs_dir\libignition-physics5-5.2.0-hef61a30_2\Library\lib\ign-physics-5\engine-plugins\ignition-physics-bullet-plugin.dll", 
"C:\bld\ros-humble-ros-gz-sim-0_1671085464153\_h_env\Library\lib\ign-physics-5\engine-plugins\ignition-physics-bullet-plugin.dll"

[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.

[Tobias-Fischer]

@conda-forge-admin, please rerender

[Tobias-Fischer]

/cc @traversaro

[traversaro]

I am currently far from keyboard, but if I recall correctly in the case of Windows if a symlink is problematic the dll is simply copied. Not installing the unversioned version will fail at runtime I am afraid. To double check we can see how all other plugins are dealt with.

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[Tobias-Fischer]

The unversioned version is still being installed via a copy. I think having both copy + symlink led to issues. According to the logs, both dlls (unversioned and versioned) are found properly now by conda-build, whereas the previous build had a 0-byte unversioned dll that caused issues.

[traversaro]

The unversioned version is still being installed via a copy. I think having both copy + symlink led to issues. According to the logs, both dlls (unversioned and versioned) are found properly now by conda-build, whereas the previous build had a 0-byte unversioned dll that caused issues.

Ok, great!