Modules determine their own compatibility with the library

A module is built against the system-installed libdpm-core.so and is
responsible for being correct against it. Where it needs to act on the
version it is running under, dpm_core_version() reports that and the
module decides for itself.

dpm_module_core_min() is removed. It was a declaration handed to the
library to enforce on the module's behalf, and enforcement of that kind
belongs nowhere in a library that routes and hosts. The contract is now
three reserved symbols and load validation is two steps: the reserved
symbols resolve, and the version and description probes return
well-formed values.

compare_versions had no remaining caller and is removed; parse_version
stays for the well-formedness probe. The core_too_new fixture went with
the handshake it existed to exercise.
This commit is contained in:
2026-08-15 04:21:58 -04:00
parent 97b39cac6c
commit 17acad2b02
17 changed files with 101 additions and 185 deletions

View File

@@ -2,9 +2,8 @@
* @file missing_symbols.cpp
* @brief Broken fixture: exports only part of the module contract
*
* Missing dpm_module_execute, dpm_module_core_min, and
* dpm_module_manifest. libdpm-core must refuse it at step 1 and
* name the missing symbols.
* Exports the version and description probes and nothing else.
* libdpm-core.so refuses it at step 1 and names dpm_module_execute.
*
* Part of the Dark Horse Linux Package Manager (DPM)
*