Now with recommends enabled, plasma-mobile images include Phosh as well

I've flashed mobian-sm6350-plasma-mobile-20260215 to my fp4 and both Phosh/Plasma are available in the login manager.

image

IMO this should be avoided, otherwise we could rather have a single "graphical" image with Phosh+Plasma, half build time, less artifacts to be managed... 😅

AFAICT issue discends from

  • phrog depending on phoc
  • phoc recommending phosh
mobian@mobian:~$ apt-cache show phrog
Package: phrog
Version: 0.50.0-1
Installed-Size: 8259
Maintainer: DebianOnMobile Maintainers <debian-on-mobile-maintainers@alioth-lists.debian.net>
Architecture: arm64
Replaces: phog
Provides: phog
Depends: dconf-gsettings-backend | gsettings-backend, libc6 (>= 2.39), libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.2.4), libgcc-s1 (>= 4.2), libgdk-pixbuf-2.0-0 (>= 2.22.0), libglib2.0-0t64 (>= 2.54.0), libgtk-3-0t64 (>= 3.19.12), libhandy-1-0 (>= 0.82.0), libpango-1.0-0 (>= 1.14.0), libphosh-0.45-0 (>= 0.45~rc1), accountsservice, at-spi2-core, fonts-lato, gnome-session-bin, gnome-session-common, gnome-settings-daemon, gnome-shell-common, greetd, librsvg2-common, phoc, phosh-common, phosh-osk-stevia, polkitd
Conflicts: phog
Description-en: Greetd-compatible greeter for mobile phones
 Phrog is a graphical greeter speaking the `greetd` protocol and aimed at mobile
 devices like smart phones and tablets using touch based inputs and small
 screens.
 .
 It was initially designed for the Phosh Mobile Environment based on GNOME/GTK
 but can spawn any graphical session.
Description-md5: adadcb98d28bb078de50004ecd77091c
Homepage: https://github.com/samcday/phrog/
Section: x11
Priority: optional
Filename: pool/main/p/phrog/phrog_0.50.0-1_arm64.deb
Size: 1553156
MD5sum: 597b682171d5fc8503f12f24fc524cc0
SHA256: cd05d762d10d4c7dd9c3614159e9222f10235706c598944fdaa6abba4048649c
mobian@mobian:~$ apt-cache show phoc
Package: phoc
Version: 0.52.0-1
Installed-Size: 1209
Maintainer: DebianOnMobile Maintainers <debian-on-mobile-maintainers@alioth-lists.debian.net>
Architecture: arm64
Depends: gsettings-desktop-schemas, mutter-common, dconf-gsettings-backend | gsettings-backend, libc6 (>= 2.38), libcairo2 (>= 1.2.4), libglib2.0-0t64 (>= 2.83.0), libgmobile0 (>= 0.6.0~beta1), libgnome-desktop-3-20t64 (>= 3.17.92), libinput10 (>= 1.9.2), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libpixman-1-0 (>= 0.44.0), libudev1 (>= 183), libwayland-server0 (>= 1.14.91), libwlroots-0.19 (>= 0.19.0~), libxcb1, libxkbcommon0 (>= 0.7.0)
Recommends: phosh, xwayland
Breaks: phog (<< 0.1.6~), phosh (<< 0.34.0~)
Description-en: Wayland compositor for mobile phones
 Tiny wayland compositor based on wlroots for use on mobile phones like the
 Librem 5.
 .
 You likely want to use Phosh (the phone shell) with it.
Description-md5: 8af74e7fa571b4f8fe179e1d99da4f9f
Homepage: https://gitlab.gnome.org/World/Phosh/phoc/
Section: x11
Priority: optional
Filename: pool/main/p/phoc/phoc_0.52.0-1_arm64.deb
Size: 227332
MD5sum: b6da6d4f7a570a1bca718ccd3e2f12e4
SHA256: 97656f99d8b3cabe306ad4ad04f06629c9b32ecc4d20d27a9bf8c5960c41de17

Is it needed for phoc to recommend phosh? I see phoc was recommeding phosh since day 1 , then maybe the aim was to avoid users shooting themselves in the foot by installing phoc rather than phosh (?)