Source: lomiri-session Version: 0.3-11 X-Debbugs-CC: [email protected], [email protected]
I believe it is best for a desktop's default metapackage to be managed by a package the desktop maintainers control instead of in a list of packages in tasksel. task-gnome-desktop and task-gnome-flashback-desktop do this. This allows the Lomiri desktop maintainers to easily change the list of installed packages without having to work through getting things done in tasksel directly. I believe the tasksel maintainers prefer that separate workflow too. Additionally, some people don't install desktops from tasksel and I think it's better for the experience to be similar across different ways of installing Lomiri. 1. lomiri-desktop-session provides /usr/share/wayland-sessions/lomiri.desktop which is essential for running lomiri from a login screen (like lomiri-greeter). Because it has that function, I think it might not be good to have it also be the metapackage for Debian's default Lomiri desktop. lomiri-desktop-session currently acts as a metapackage because of the large number of apps it recommends that aren't essential for a Lomiri session. 2. task-lomiri-tablet feels unusual to me. It makes lomiri-keyboard a dependency instead of a recommends and then installs fewer apps. Is there any reason why we can't make lomiri-keyboard a dependency for the regular metapackage too? The Lomiri tablet task is unusual in that it is not presented during install, but only as an option afterwards https://salsa.debian.org/installer-team/tasksel/-/blob/master/tests/tablet Which apps make sense for Lomiri Desktop but not for Tablet? And are the dependencies even set up to do that correctly? 3. Similarly, lomiri recommends lomri-desktop-session | lomiri-touch-session but the touch session package doesn't exist yet. What would be different about it? 4. Some desktops have an advantage where their metapackage is named simply: - gnome - lxde - xfce4 We could do that for lomiri by renaming the existing lomiri binary package to lomiri-shell and then using the lomiri binary package to be our metapackage. That would allow us to keep the current install instructions from https://wiki.debian.org/Lomiri and https://lomiri.com/#install-lomiri which is apt install lomiri. 5. In addition to 'gnome', there is 'gnome-core' which is upstream's definition of GNOME Core, with some minor tweaks for Debian. I expect that there will eventually be a 'gnome-minimal' for people who want GNOME without so many apps (but the GNOME maintainers haven't gotten around to deciding how minimal it needs to be). There is 'kde-standard' (default Debian KDE install), 'kde-full' and 'kde-baseapps'. We could follow the GNOME style and add a 'lomiri-minimal' if we want to have a layer between the Lomiri shell and our default metapackage. We could also add a metapackage to recommend all Lomiri style apps since we are now packaging apps that we might not want to install by default but some people may want an easy way to install them. This could be named something like 'lomiri-extras' or 'lomiri-full'. Thank you, Jeremy Bícha
