search

conda-forge / imath-feedstock

A conda-smithy repository for imath.
BSD 3-Clause "New" or "Revised" License
0 stars 5 forks source link

Wrong run_exports info? #7

Closed traversaro closed 1 year ago

traversaro commented 1 year ago

Solution to issue cannot be found in the documentation.

Issue

I experienced some error:

$SRC_DIR/build/bin/ClockTest: error while loading shared libraries: libImath.so.29: cannot open shared object file: No such file or directory

in https://github.com/conda-forge/staged-recipes/pull/21891#issuecomment-1458158474 .

It seems that the error is related to imath 3.1.7, that bumped the soversion from 29 to 30 w.r.t. to imath 3.1.6 , see https://github.com/AcademySoftwareFoundation/Imath/commit/a4f9d5c6205482e1f1a86c84bb97bafa247fb774 . Given that the soversion is changing in patch versions, should we change the run_exports from:

    - {{ pin_subpackage(name|lower, max_pin='x.x') }}

to

    - {{ pin_subpackage(name|lower, max_pin='x.x.x') }}

?

Installed packages

Not relevant.

Environment info

Not relevant.
traversaro commented 1 year ago

fyi @conda-forge/imath .

traversaro commented 1 year ago

From what I understand in the upstream issue (in particular https://github.com/AcademySoftwareFoundation/Imath/issues/189) it seems that there is still no strict policy on soversion changes. Given this confusion, I think it probably make sense to just switch to max_pin='x.x.x' and do a repodata patch while upstream decides.

traversaro commented 1 year ago

It seems that a few users are hitting this:

I think it is better to proceed: