# RootsLanding Windows Store 0.2.2.0 — Qt/PySide6 replacement information

## Status and scope

RootsLanding 0.2.2.0 uses PySide6 6.11.1, Shiboken6 6.11.1, and Qt 6.11.1 under the LGPL-3.0-only option. They are separate files in the package; the audit found no static Qt linking and no RootsLanding modification to Qt/PySide source.

The replacement-and-sideload pathway below is an engineering pathway identified from the package layout and Microsoft documentation. **RootsLanding has not completed an end-to-end test using an interface-compatible rebuilt Qt/PySide library and does not represent this workflow as tested.**

## Corresponding source

- Qt for Python / PySide6 6.11.1: https://download.qt.io/official_releases/QtForPython/pyside6/PySide6-6.11.1-src/pyside-setup-everywhere-src-6.11.1.tar.xz
- Qt 6.11.1: https://download.qt.io/official_releases/qt/6.11/6.11.1/single/qt-everywhere-src-6.11.1.tar.xz
- Qt third-party license index: https://doc.qt.io/qt-6/licenses-used-in-qt.html
- Qt WebEngine/Chromium licensing: https://doc.qt.io/qt-6/qtwebengine-licensing.html

## Separate library locations

Within the unpacked RootsLanding application payload, relevant files are located under paths including:

- `_internal\PySide6\*.pyd`
- `_internal\PySide6\Qt6*.dll`
- `_internal\PySide6\plugins\...`
- `_internal\PySide6\QtWebEngineProcess.exe`
- `_internal\PySide6\resources\...`
- `_internal\shiboken6\*.pyd` and related runtime DLLs

Any substitutes must remain interface-compatible with the RootsLanding application and with each other.

## Untested engineering pathway

1. Obtain the preserved Store-upload package and unpack it into a working directory.
2. Build interface-compatible PySide6 6.11.1, Shiboken6 6.11.1, and Qt 6.11.1 libraries from the corresponding source.
3. Replace only the corresponding separate libraries, plugins, executables, and resources in the unpacked package.
4. Repack the working directory as an MSIX.
5. Create a development code-signing certificate whose subject matches the package manifest Publisher, sign the repacked package, and trust the certificate on the test device.
6. If Windows reports a same-identity conflict, back up the RootsLanding data, remove the Store-installed copy on the test device, and then sideload the modified package.
7. Test startup, Qt Widgets, Qt WebEngine preview, image import, local preview, and publishing preview. Record all commands, tools, hashes, and results.

Microsoft Store signing and package content enforcement prevent an installed Store package from accepting a simple DLL overwrite while retaining Microsoft's signature. A repacked package must be signed and trusted under Microsoft's sideloading rules.

## Requesting preserved materials

Email `contact@rootslanding.com` with “RootsLanding 0.2.2.0 relinking materials” in the subject. Identify the release and the materials you need. RootsLanding will provide the preserved release-specific materials available for exercising applicable open-source license rights.

Modified packages are unsupported. Back up all irreplaceable family material and use a dedicated test environment.