The evolution of packager managers

In the early days of Linux, installing software applications was much more difficult. Most software was not distributed in easy-to-install packages. I frequently had to download source code, which usually came as a ‘tar’ file that had to be extracted and then compiled to run on the system. There was usually a four-step process which included extraction, change to the directory where the uncompressed files resided, and then issuing a series of commands which included:

$ ./configure

$ make

$ make install

• ./configure checked your system for dependencies and set up build options
• make compiled the program from source code
• make install copied the compiled files into system directories (usually /usr/local)

Then Linux distributions began to provide software in precompiled packages for compatible systems. Debian developed .deb packages, which were installed with the dpkg command. Red Hat developed RPMs, which were installed but still had dependency issues. A typical install on a Red Hat system looked like this:

$ rpm -i somepackage.rpm

The command above installed the package but provided no visual or other feedback. Therefore, I often used the following command when installing a package:

$ rpm -ivh somepackage.rpm

• i – tells the package manager to install the package
• v – tells the package manager to produce a verbose output
• h – displays a progress bar made of hash marks

The process became much more appealing with the development of automated package management, which began with Debian’s APT (Advanced Package Tool) in 1998. This was followed by YUP (Yellow Dog Updater), originally created in 1999 as a backend for Yellow Dog Linux. YUP was later rewritten as YUM (Yellow Dog Updater Modified) and was primarily used at Duke University to update Red Hat systems. However, even with these advancements, it was still uncertain whether all dependencies were being met. Since then, a rewrite of YUM, DNF (Dandified YUM), was introduced in Fedora 18 in 2013. Arch Linux and Manjaro use pacman, a package management system that has revolutionized software installation on Linux systems.

In conclusion, the evolution of package managers has significantly transformed the Linux landscape, making software installation more efficient and user-friendly. From the cumbersome process of manually compiling code to the sophisticated automated systems we use today, the advancements in package management have not only simplified dependency resolution but also enhanced overall system stability. With tools like APT, YUM, and pacman, users can easily access, install, and update software with minimal hassle, paving the way for broader adoption and greater innovation within the Linux community. As technology continues to advance, we can anticipate further improvements that will streamline software management and empower users to leverage the full potential of their operating systems.