Are there any (functional) Differences between Installation of Packages in Calamares versus CLI later on?

Actually there are three different options available to install packages in EOS.

1. By selecting them in Calamares-installer:

2. By installing them via CLI-command after finishing base system installation:

$ sudo pacman -Syyu wpa_supplicant networkmanager blablabla

3. By using Discover to install them via GUI after finishing base system installation

(I guess, no screenshot required here :wink:)

So my questions especially about the category Base-devel + Common packages group are:

  • Are there any differences regarding package function why I should choose one option over the other? (e.g. installing wpa_supplicant during installation or later on via CLI)
  • Do the packages get pre-configured differently when I install them via Calamares-installer in comparison to CLI?
  • Do all packages of Calamares exist with identical names within the repos (to install them easily via CLI later on, using the same names)?
  • Or does Calamares provide something like Calamares-specific meta-packages (that technically don’t exist in reality) but contain a group of “real” packages to get the desired package to work?

If the latter is true, I couldn’t install them via CLI because I wouldn’t know what else Calamares has installed to get the package working. Therefore better to ask here. :slightly_smiling_face:

Furthermore, some packages seem to be mandatory to install them during initial installation already. See here for example the package ethtool:

in the online part of calamares , the desktops are installed in Groups. if it was installed in in Meta packages it get also harder to remove some packages if you dont want it.

all things are configured as vanilla. you can make your desktop of your own also.

if you use online installer your system is already up2date do pacman -S xxxx is fine but general, de groups packages in endeavouros is basicly al what you need to run a desktop. :slight_smile: calamares is just a installer btw ; if you do pacman -S plasma , it installs all from ‘group’ plasma… groups are basicly different then packages it self, packages self are mostly : package+depency thats needed… but groups are , packages in a group+ depencys what needed.

1 Like

Thank you for your answer! :smiley:

Okay, the Desktop Environment group is a bad example with all its meta packages, I should precise my question more about the Base-devel + Common packages group. :smile:

Recommended NOT change or uncheck them if you do not know exactly what you do :wink:

In the end there is no difference as installer is also using pacman to install the packages selected. But installing packages on installed system is not possible with calamares, it is only the initial system installer (also using the tools from archlinux to install needed packages)

You can uncheck packages if you are sure you do not need them inside install procedure but you can also remove them on installed system later…

We do some basic preconfigurations like enable needed services (systemd) and configuring boot process and DM (Login Managers) and some theming is also done from installer…

1 Like

To be clear, ethtool is useful and I would recommend it but I don’t see it as a required component of a base install. You don’t need it to connect to the network. It is useful for when specific situations come up that require changing adapter settings such as when duplex auto-detection isn’t working.

base-devel is needed to install AUR packages.

1 Like