How to handle cyclic dependencies with Simulink libraries ?

We have the following usecase:

We created a library "Std_Lib" that contains certain utilities and is tracked on git, let's say this library has the following versions: V1.0.0, V2.0.0

We created another libraries "Algo1_Lib" that depends on "Std_Lib" V1.0.0 and "Algo2_Lib" that depends on V2.0.0.

We are using git submodule to handle depedency resolution.

However V1.0.0 and V2.0.0 contains the same names, is there any way to handle this in a Simulink project ? That V1.0.0 should be used with Algo1_Lib and V2.0.0 should be used with Algo2_Lib ?

Edit:

S-Function would not be a suitable solution as I want to use the signal size inheritance that can be used with libraries.

[Walter Roberson]

If I recall correctly (I might not!!) signal size inheritence can be used with Level-2 S Functions that are programmed appropriately... but it might not be straight-forward.

[Mohamed-Marwan Chawa]

Thank you Walter, will give it a try and report back.