Compile it yourself for performance
Are you worried that most of your software sucks resources out of your system like a wet sponge? Then you’ll be interested in Suckless Tools (https://tools.suckless.org). All the tools in this series have been designed to be as small as possible, even when some functionality is sacrificed. But when would you use them? Well, you can usually live with a regular system, but when you have a small system or a background process such as mining, you might want to use Suckless Tools to have another machine available for commands.
In this tutorial, we’ll learn how to compile and patch the most common parts of the Suckless Tools. You will be able to transition over to a smaller system without killing your current system. This way you can get used to the new ways of running your computer.
Get set for sucking
You need to have the essential development tools for compiling C: gcc is the most common choice. However, the project considers that a bloated piece of software too, so don’t ask them for help with gcc.
We’ll use gcc though, since it will probably already be installed on your system. Otherwise, your best bet for getting the source is to set up a directory where you clone each package into its own directory. Then add a patches directory and you are good to go. If you want to publish your unique masterpieces, create forks with git:
After you have run these two branch and then publish to GitHub or any server. You can also send any brilliant changes to the Suckless Tools by using git’s send-email functionality.
