As a molecular modeler, you likely rely on various extensions to enhance your workflows. However, if you’ve ever faced issues with extensions not loading or functioning as expected, it might come down to version compatibility between SAMSON and the Software Development Kit (SDK) used to build the extensions. Let’s clarify how compatibility works and how you can manage these challenges effectively.
How SAMSON Ensures Compatibility
When you start SAMSON, it checks the version number of its own SDK against that of each installed extension. An extension will only be loaded if its SDK version is compatible with SAMSON’s version. This preventive measure ensures that incompatible extensions cannot disrupt your work or compromise performance.
What Does Compatibility Mean?
SAMSON adheres to semantic versioning principles, using the format major.minor.patch for version numbers. Compatibility between SAMSON and an extension is maintained if:
- The major version numbers of both SAMSON and the SDK are identical.
- The SDK’s minor version number is smaller than or equal to SAMSON’s minor version number.
For instance, SAMSON version 1.7.8 is compatible with SDK versions 1.3.5 and 1.7.7, but not with SDK version 1.8.5, as the latter introduces changes that SAMSON 1.7.8 cannot recognize.
The Benefits of Automatic Updates
An additional perk of SAMSON is its automatic update feature for extensions. As long as your version of SAMSON is compatible, it will automatically download and update extensions to their latest versions available on SAMSON Connect. This ensures you always have access to the latest features and bug fixes.
Practical Implications
To illustrate how this works, consider the following scenarios:
- If you’re using SAMSON version 1.7.8 with an extension built on SDK version 1.5.2, the extension will function seamlessly as the major versions match, and the SDK’s minor version is compatible.
- If a new extension version built with SDK 1.6.4 is released, SAMSON will update the extension automatically because it’s still compatible with SAMSON 1.7.8.
- However, if SAMSON 2.0.0 and its SDK are released, an extension built with SDK 2.0.0 will not work on SAMSON 1.7.8. In such cases, updating SAMSON is necessary to use the new extension version.
Keep SAMSON Updated
For molecular modelers, staying on top of updates is more than a matter of convenience. Updating SAMSON ensures you’re working with the most recent features and that your extensions remain functional. SAMSON’s backward compatibility policy helps avoid disruptions while encouraging a smooth transition to newer versions.
To dive deeper into version compatibility and how it applies to your workflows, visit the official documentation: Learn more here.
SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON now from SAMSON Connect.