Archlinux is a rolling release. That means you do not need to do a clean install to get the latest version. But there might be reasons why you actually should or want to do that :

  • you ‘abused’ your system with errors as consequence
  • you are learning about archlinux and test things out
  • you have installed too many applications and dependencies
  • you want the latest customizations of Archlabs (~/.config folder)

For all these reasons and more it is best to do a clean install. People ask if I do dual boots (different operating systems on one ssd). As a rule I never do a dual boot. I open up my desktop computer and change ssd’s. I also let the installation media of the distro decide about partitions (number and size). No complex partitioning for me. When all is installed I will install two cloud services: dropbox and insync (google drive). I will select which folders I want to sync to the ssd. As a backup I can hook up an external harddisk.

When writing this article Archlabs 4.0.0 is the major release and at this time the parts that make up Archlabs are NOT a rolling release.

In the roadmap it has been decided to make Archlabs as much as possible a rolling release so you do not have to reinstall from scratch. Next versions  (Archlabs >4.0.0) will be able to do this and betatesters are trying out the newest beta-releases right now. You can make your Archlabs 4.0.0 already somewhat more ‘rolling’ if you want to give it a try. you can follow this link for the tutorial. 10 Archlabs AUR packages have been added to make Archlabs a rolling release. You can find them in the description.

Or you can simply wait for the next iso release.

However we can never make a rolling release from your HOME DIRECTORY.

It is somewhere in the guidelines of Archlabs Packaging GuideLines that we have to stay out of the users folder. And if you think about it; that is common sense. But if we want to  have a rolling release that makes things a bit more complex.

The archlabs-conky’s can be updated via a script: ~/.config/conky and is explained in this article.

The archlabs config files will have to be compared by you manually: ~/.config/openbox.
That is the topic of this article!

All the rest of the ~/.config files for neofetch, termite and so many others are ONLY on the iso and will never change automatically. That might become a reason to do a clean install.

In this tutorial we will compare our own ~/.config/openbox folder with the latest config from Archlabs from the github: https://github.com/ARCHLabs/Archlabs-Openbox-Configs

What does it contain?

It contains logo’s to be used at your discretion.
It contains scripts to make your life easy and efficient.

  • delete the virtualbox applications when you have decided to install archlabs to a ssd or harddisk
  • get the latest archlabs conky collection from the net in ~/.config/conky
  • get the latest kernel and install it
  • fix icons that normally never change with any icon theme

It contains the autostart. Hashtag out lines you do not want to execute.
It contains menu-obmenu-generated.xml. Alternative to the standard menu.xlm explained here.
It contains menu.xml. This is the standard menu from openbox.
It contains rc.xml. Settings and shortcuts for openbox.

These files will change over the coming months and years.
From time to time you can come to the github and compare them with the super tool : meld.

I have just added rofi to the possibilities of Archlabs. It is already online but my local config is not up-to-date yet. More Rofi information.

Let us update our local config folder.

 

Pin It on Pinterest