Logonomic Linux library source and replacement

The project's adopted Qt distribution basis remains LGPL-3.0-only. The
selected contract identifies the actual Qt version; this instruction does not
extend an earlier version's binary or source evidence to another version.

The legal bundle identifies the exact Qt, ICU and Ubuntu runtime binaries and
their corresponding source materials. The Qt contract and prepared input must
agree on their version and contract digest. A retained input for another Qt
version is not evidence for the libraries delivered in this package.

The shared Qt and native-runtime material may describe the supplier's Soter
layout. In the Logonomic desktop payload, the corresponding application-local
libraries are in lib beside logonomic. The paid broker's private libraries are
in software-lock/soter_runtime/lib. The separately manifested Soter for Logonomic
recovery subtree keeps its own recorded layout and legal materials. The package
content manifest records the delivered paths and hashes; supplier source
contracts retain their original paths and bytes.

For each Qt module, use the exact source archive, build/modification information
and replacement instructions provided in the Qt materials. For an Ubuntu
library, find its source package/version and source archive descriptors in
linux-runtime-bundle.json or linux-paid-runtime-bundle.json. Extract the supplied
source descriptor with dpkg-source -x, install the build dependencies named in
debian/control, and use the supplied debian/rules through dpkg-buildpackage to
build a modified library. These source materials retain their controlling
licences, notices and patches. ICU retains its separate vendor licence.

Close Logonomic and all its terminal sessions before replacing a library, and
keep a backup. Build an interface-compatible shared library with the same
expected SONAME and filename. Preserve its relative ELF search path and keep
its dependencies available. A library in lib normally uses $ORIGIN; plugins and
QML libraries need their original relative path back to lib. The delivered
qt.conf selects the neighbouring plugins and qml directories. Replace matching
plugins and QML libraries together when their interfaces require it.

Installed packages

The Debian and Qt Installer Framework packages launch logonomic directly from
the installation directory (normally /opt/varinomics/Logonomic). Replace the
applicable shared library there, or copy the complete installation into a
separate directory you own and replace it in that copy. Preserve the directory
layout, executable modes and qt.conf. Launch that directory's logonomic as your
normal desktop user. Changing a system-owned installation requires normal
administrator permission.

AppImage copies

AppRun verifies the original package inventory and its retained application-data
copy on every launch. Modifying that retained copy makes verification fail;
--appimage-extract-and-run still invokes AppRun and has the same constraint.
Keep the original AppImage and its retained copy intact. For a modified local
copy, use the runtime's extraction operation in a new working directory:

    ./logonomic.AppImage --appimage-extract
    cp -a squashfs-root/contents "$HOME/logonomic-modified"

Use the actual downloaded filename, and choose a new destination directory.
The resulting installation root is $HOME/logonomic-modified/payload. Replace
the shared libraries in its lib directory and matching plugins or QML files in
its plugins and qml directories, preserving the layout described above. Then
launch the native entry directly:

    "$HOME/logonomic-modified/payload/logonomic"

This direct entry does not invoke AppRun's retained-copy check. Do not launch
the modified tree through AppRun or change the original inventory to make it
appear unchanged. Keep the extracted tree until all its terminal sessions have
ended. Its legal directory retains the same source-access and build materials.

Paid editions still require the normally provisioned activation broker and a
valid activation. Library replacement does not provision that service. The
broker's active system libraries are separately installed under
/usr/lib/varinomics/software-lock/soter_runtime/lib; changing the private
software-lock directory in an extracted application does not change that
running service. Its administrator controls service-side library changes.

These instructions use dynamic shared-library replacement, with the supplied
source and build information for rebuilding those libraries. They do not claim
an application object-file relinking kit. Varinomics does not require a vendor
signature for the modified libraries in this directly executed copy. The
Logonomic Agreement preserves the controlling third-party replacement and
debugging rights.

This instruction is not an assertion that all runtime source inputs are present.
The release exporter separately verifies the exact selected libraries, supplier
contracts, prepared source archives, notices and Qt deployment before admitting
a package.
