The point is, that tigervnc is not needed for some setups. And tigervnc itself depends on many packages itself. And each dependend package could have dependencies itself. In fact we get a dependency tree, and potential problems without any need. So if someone wants to use thightvnc and xrdp that's not possible because tigervnc blocks installation of tightvnc. The clean way is to define only those packages as dependent which are realy depend. The other packages belong to optdepends.
By the way. What is the answer to this question: Why tigervnc is defined as dependency while xorg-xrdp ist not?
Pinned Comments
Abzie commented on 2024-05-10 14:40 (UTC)
If upgrading from 0.9.x, please read the 'User Changes' section from the release page:https://github.com/neutrinolabs/xrdp/releases/tag/v0.10.0
There is one breaking change that require manual intervention but there are three other changes that will continue to work for now.
xRDP states: Users are urged to heed any generated configuration warnings and update their configurations. Later major versions of xrdp may remove these warnings, or introduce other behaviours for the affected parameters.