Asked for suggesions, I find it confusing that have a pop-up at all, irrespective of the wording or the message unless I can link that pop-up to a specific action of mine.
So one suggestion to implement a AUR “warning” or an “AUR educational bit” would be to either implement it in the first start Manjaro-Hello (then it will likely be overseen), or to do a first run wizard.
A first-run wizard (frw) may be low complexity one (e.g. a mere slideshow with infos and “stupid” ‘Next’ buttons), or in form of a GUI that indeed leads to some sort of (optional) configuration.
Just an Example:
First page or tab (or whatever) of frw gives Information about the package management options and asks for (e.g.)
- do you want to enable checking for automatic updates (y/n); (recommendation: y)
- if y, how often do you wish to check for updates [set value];
- do you want to remove orphaned packages after uninstalling packages from the system (y/n) [Warning: occasionally packages may be designated orphans, but are actually needed by other packages; plus --> Link to possibilites to clean up system> (recommendation: n)
- how many versions of installed packages do you whish to keep in the package cache [set value] (recommended: 2) plus Info: what is the package cache and how to use it plus --> Link to package cache wiki with info how to downgrade packages>
Second page frw:
- Do you want to update mirror sources now (y/n) (recommendation: y)
- Do you want to change to update servers nearby (y/n) (recommendation: y)
Third page/tab of frw:
Information about AUR plus then asking:
- Do you whish to enable AUR support?
- Do you whish to monitor updates from AUR?
- Default build folder is /tmp (provide possibility to change)
At the end of the frw, the password is asked for and the respective settings are made.
One could also call it Package Management Wizard and keep it for later use (and just have it started first time on first boot automatically, or have it start when first time calling the Package Manager in order to link this type of information with what the user actually was starting to do (managing packages).
I think this would really bring the messages over to those new to Arch/Manjaro and be a nice aggregation of configuration options for those sticking with Manjaro (in particular those who prefer to work with the system on not constantly on the system ;-).
If agreed on the general idea, I may think of a more detailed implementation and start a Feature Request Thread.