Adding a dependency can cause unintended side effects. For example, users may now (directly or indirectly) pull in a package that conflicts with something else they have installed. Have you looked for these? Does the alternative provided definitely cover all cases?
> I believe the portal backends currently open by default in the locale sort order, so xdg-desktop-portal-gnome is preferred if installed, then xdg-desktop-portal-gtk, then xdg-desktop-portal-kde, then xdg-desktop-portal-wlr. Which coincidentally is the order we would want.
Could this therefore cause user behaviour to change as a higher priority backend is dropped in? Again, has this been analysed?
It might all be fine, but these are the sorts of things that I think need documented analysis in the "What could go wrong" section.
> What Could Go Wrong
Adding a dependency can cause unintended side effects. For example, users may now (directly or indirectly) pull in a package that conflicts with something else they have installed. Have you looked for these? Does the alternative provided definitely cover all cases?
> I believe the portal backends currently open by default in the locale sort order, so xdg-desktop- portal- gnome is preferred if installed, then xdg-desktop- portal- gtk, then xdg-desktop- portal- kde, then xdg-desktop- portal- wlr. Which coincidentally is the order we would want.
Could this therefore cause user behaviour to change as a higher priority backend is dropped in? Again, has this been analysed?
It might all be fine, but these are the sorts of things that I think need documented analysis in the "What could go wrong" section.