Add ocpsvg

[ndevenish]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/ocpsvg/meta.yaml) and found some lint.

Here's what I've got...

For recipes/ocpsvg/meta.yaml:

• The home item is expected in the about section.
• The summary item is expected in the about section.

[conda-forge-webservices]

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 (recipes/ocpsvg/meta.yaml) and found it was in an excellent condition.

[hmaarrfk]

is this really necessary? can you show me the errors without it?

[hmaarrfk]

The reason is that we've started to remove these from other builds:
conda-forge/qt-main-feedstock#287

[ndevenish]

https://dev.azure.com/nicholasdevenish/feedstock/_build/results?buildId=178&view=logs&j=6f142865-96c3-535c-b7ea-873d86b887bd&t=22b0682d-ab9e-55d7-9c79-49f3c3ba4823&l=1176 but I've rerun it in here

[ndevenish]

import: 'ocpsvg'
Traceback (most recent call last):
  File "/home/conda/staged-recipes/build_artifacts/ocpsvg_1724522226129/test_tmp/run_test.py", line 2, in <module>
    import ocpsvg
  File "/home/conda/staged-recipes/build_artifacts/ocpsvg_1724522226129/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold/lib/python3.12/site-packages/ocpsvg/__init__.py", line 1, in <module>
    from .svg import (
  File "/home/conda/staged-recipes/build_artifacts/ocpsvg_1724522226129/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold/lib/python3.12/site-packages/ocpsvg/svg.py", line 22, in <module>
    from OCP.BRepAdaptor import BRepAdaptor_Curve
ImportError: libGL.so.1: cannot open shared object file: No such file or directory

[ndevenish]

[gestures towards failed tests]

[ndevenish]

The other mechanism I know about to deal with things like GL are the CDT packages; which I believe is to compile against things that should be present at runtime; but running the tests effectively are runtime, hence needed.

Maybe I only need to add the runtime here; mesa-glu-devel is how I’ve seen it solved before, perhaps I need to be more targeted in just picking up the runtime? I think I was under the impression there was a small allowlist of things that can go here.

[hmaarrfk]

lets see what happens with:

conda-forge/ocp-feedstock#50

[ndevenish]

Otherwise, I think this is ready - thank you - shall I ping or will you merge it directly?