YunoHost app package dependency conflicts with core system libraries

YunoHost employs a custom packaging system where applications are deployed via a manifest and a set of scripts (install, remove, upgrade). This architecture allows for community-driven app repositories that operate independently of the core operating system updates.

A design challenge arises when an application package requires a specific version of a system library that differs from the version required by the YunoHost core environment. Because the system typically relies on system-wide dependencies rather than fully isolated containers for every app, there is a potential for version mismatch during the yunohost app install process.

• How does the YunoHost API handle dependency resolution when a package manifest requests a library version that conflicts with a core system requirement?
• Is there a documented mechanism within the packaging guidelines to implement isolated environments for specific app dependencies without compromising the centralized management of the server?