Eventually people will figure out that they can use the pkgs.txt file on the live ISO and install any package that’s in the Arch repo. All AUR packages have to be installed afterwords with yay which is extremely easy and fast. I don’t think it should be up to EndeavourOS devs to tell people what should or could be installed. The Welcome app has the list of ALL available packages both in the Arch repo and the AUR. All they have to do is check if what ever they are looking for is there. Then install it by either method required.
Not sure if this would help you, but EndeavourOS installer supports inserting your own list of additional packages.
A simple way is to write package names into file /home/liveuser/user_pkglist.txt and then install in the online mode. This will install the default packages listed by EndeavourOS, and then your additional packages from that file.
Another way to install is to close the Welcome window and restart it from the terminal:
This way you can give an URL that refers to a file (e.g. at github if you have an account there) that contains a similar list of additional packages, and they will be installed like above.
Edit: oh, didn’t see that @ricklinux had already answered this.
I think having a commonly used package list in installer might induce some friction in the install process. The installer is aimed at providing a quick installation of an Arch base with a simple DE.
“Commonly used” also varies from person to person. I don’t use Firefox. I don’t use office apps (like LIbreOffice). I don’t keep any media editing apps on my system. None of the “commonly used” apps I have seen in installers ever suited me.
About having your “commonly used” apps - you can add them before starting installler. This link posted also has a video demonstrating the process.
What I personally like to do is to have a text file with all the packages I want on my new systems. Then I run pacman -Syu on it after installing the distro. I like this since it will work on any arch based distro. I don’t need Calameres installer for that. Quite like what dalto suggested.
Not the same list - but automation of installation is still possible by feeding requests to yay. If you get to that point, I fire off an example or two (I have a lot of systems up, and I have an automated ‘populate’ script for all the Arch-based ones)
yay -S --noconfirm brave-bin
Because of the --noconfirm, be sure of what you want! Replace brave-bin with whatever package you want…