Improvement / UX: Please add "Install Printer Packages" to Cachy Hello / as Terminal quick-link / as daemon watching user interaction with settings

[rorar]

Hey,

While installing CachyOS over the LiveOS, it was possible to enable Printer Support.
I didn't catch that because it's so far hidden below the software package checklist.

I've found the solution to install the printer software right here:
https://discuss.cachyos.org/t/no-printer-option-in-settings/9163/2
and here for universal printer drivers gutenprint and foomatic-db-gutenprint-ppds
https://discuss.cachyos.org/t/missing-packages-while-install-canon-printers-driver/3354/7

But you know... Most time the most important papers needs to be printed last minute and there's no time for a search. :)
Also... If your internet connection is down, you're pretty screwed.

Therefore I'd love to have some simplified options:

• While installing: Please highlight the Printer Support, maybe as own slide
• Keep a copy of the printer packages + gutenprint as fallback offline version in the system
• Post Installation "fix": add an option to install Printer Packages and drivers from
  • Cachy Hello
  • terminal sudo install-print-packages or with the fun command printmelikeoneofyourfrenchgirls
  • as a daemon/watchdog; if the user interacts with the printer settings and cups isn't installed, propose the installation over a notification

Let me know your thoughts!

[ptr1337]

I think we could merge CachyOS/cachyos-calamares#126, which would help that printer support is not so much down.

We will discuss it in the team how we want to proceed there.

It would be sad tough loosing the capatibility to remove specific packages from the desktop installation, but would avoid a bunch of issues as well as highlighting the printer support better.

[rorar]

Hi Peter, to hit the arch ("um den Bogen zu schlagen")...

1. The installation routine has grown out of its existence and should have UX/UI overhaul.
2. This includes the post installation routine as well (Cachy Hello).

In this case, this/my issue belongs more likely to the post installation routine. :)