That’s a nice list, but a brief explanation for each package would be very helpful. As a beginner I have no clue what most of them do. I chose Arch because I do not want to fill up my system with software I never use, copy pasting this list would defeat the purpose…
This is very bad advice. The point of Arch is to install what you need because you have learned why you need it.
Installing random packages because an Internet blog says you should? Many of these are specific to what choices you have made on your computer.
youtube-dl should probably be replaced with yt-dlp.. but I like Firefox, Thunderbird, vlc, git, keepassxc... I don't think that I ever needed to install sudo though... you are missing a lot of gems, like Blender, GIMP, Inkscape, nmap, mutt, irssi, gparted, jedit, go, unrar, wireguard-tools, syncthing, obs-studio, audacity...
the command below appears to list packages installed by the user:
comm -23 <(pacman -Qqett | sort) <(pacman -Qqg base -g base-devel | sort | uniq)
This is just a list of packages the author uses and isn't even specific to Arch. I am not sure it is actually useful to anyone.
pulseaudio should be replace pipewire and sudo by doas
I would also add:
- htop
- mc
- fish (or zsh)
- yay (from aur)Screw it, just pull in the entire default repo and call it a day.
With how cheap disk space is now, I wonder how infeasible this would actually be. How much disk and bandwidth would this take for, say, Ubuntu, or Arch, or Arch plus the AUR?
Once everything is installed, the package manager could handle incremental updates rather painlessly if you ran them often enough. Conflicting packages might pose a bit of an issue. But we could just exclude any package with conflicts outside of the base install, leaving it to the user to resolve.
Awk (as gawk) and iproute2 are part of a base arch install. There's no need to install them separately.
> followed by a long period where you regularly discover missing tools
Installing packages precisely when I need them helps me keep my system minimal.