You can get the default package list by searching the installer
Most of what I’ll offer will be current (may not work without access to our unstable repo). You will also need our keyring installed or disable verification for our repos in your pacman.conf.
# base install
BASE_PKGS="base xorg xorg-drivers sudo git gvfs gtk3 libmad libmatroska tumbler "
BASE_PKGS+="playerctl pulseaudio pulseaudio-alsa pavucontrol pamixer scrot xdg-user-dirs "
BASE_PKGS+="ffmpeg gstreamer gst-libav gst-plugins-base gst-plugins-good bash-completion xterm"
# installed when a user selects any of the available WM/DE
AL_BASE_PKGS="archlabs-keyring archlabs-icons archlabs-fonts archlabs-themes "
AL_BASE_PKGS+="archlabs-baph archlabs-wallpapers archlabs-scripts archlabs-skel-base"
# installed only for openbox, i3, xfce4, awesome, fluxbox, dwm, and bspwm
WM_BASE_PKGS="arandr nitrogen polkit-gnome network-manager-applet "
WM_BASE_PKGS+="volumeicon xclip exo laptop-detect xdotool compton wmctrl feh "
WM_BASE_PKGS+="gnome-keyring dunst gsimplecal xfce4-power-manager xfce4-settings"
For openbox install all of it. You will also need the relevant skel packages:
archlabs-skel-openbox which will pull in more required packages used by each WM (eg. obkey for openbox)
ksuperkey in combination with a keybind in the WM (Alt-F1 by default) to allow opening it with a single key. You can get the command from
/etc/skel/.xprofile once the
archlabs-skel-base package is installed, there is already all the stuff setup in our skel packages for this to work if ksuperkey is installed.
For the keybinds you would do that in your WM (~/.config/openbox/rc.xml for OB)
We’re moving away from including polybar for the future so I suggest installing the AUR package instead of our
archlabs-polybar if you want to use it (the latter will eventually be removed from our repos). But you can get our default configs here https://bitbucket.org/archlabslinux/pkgbuilds/src/master/archlabs-polybar/ (the scripts and configs folder).
I’m gonna skim over it because the polybar wiki covers all this stuff, but we also used a wrapper script
al-polybar-session to load polybar and do some setup/dynamic module stuff. Without using this script you will have errors/oddities with our default configs.
When I talk about skel stuff please understand that you will have to copy files or specific bits from things in
/etc/skel to your own home directory, they are not used otherwise. This is normally done for you when creating a new user with
Let me know if you run into any issues.