diff options
Diffstat (limited to '_blog')
| -rw-r--r-- | _blog/suckless-software.md | 31 |
1 files changed, 15 insertions, 16 deletions
diff --git a/_blog/suckless-software.md b/_blog/suckless-software.md index 86fb5bc..97d437e 100644 --- a/_blog/suckless-software.md +++ b/_blog/suckless-software.md @@ -1,5 +1,5 @@ --- -title: How I manage Suckless software packages +title: How I manage Suckless software installations date: 2025-11-30 layout: post --- @@ -13,8 +13,7 @@ versions are released. ## Initial setup When using a suckless program, I usually begin by cloning the project and -setting the remote URL to push a copy of the source code with my patches to my -own git repository: +setting the remote push URL to my own git repository: ``` git clone git://git.suckless.org/dwm @@ -23,28 +22,28 @@ git remote set-url --push origin git@git.asciimx.com:/repos/dwm ``` This way, I can pull updates from the upstream project whenever I want, while -committing my changes to my own git repository. The git reset command aligns my +committing my changes to my git repository. The git reset command aligns my branch head with a stable release before applying patches or installing the software. If all I want to do is reconfigure the software (e.g., change key bindings), which is what I need most of the time, the recommended approach is to modify -the config.h file. If the config.h isn't yet in the project, the following -command generates it from the defaults and compiles the software using `make -clean <target>` here `<target>` is the name of the application (e.g., dwm) -found in the Makefile. I modify the resulting config.h file and run `make clean -install` to install the software before committing and pushing my changes to my -git repo. +the config.h file. If the config.h isn't yet in the project, the +`make clean <target>` command will generate it from the defaults and compile +the software. The `<target>` is the name of the application (e.g., dwm) found +in the Makefile. I modify the resulting config.h file and run `make clean +install` to install the software before committing and pushing my changes to +the git repo. ## dwm and slstatus Since dwm and slstatus are always running, `make install` will likely fail for -them. The operating system will prevent the installer from replacing running +them. The operating system may prevent the installer from replacing running executables with new ones. Hence, we must first stop the running instances of -these programs (Mod + Shift + q). Then, switch to a tty (Ctrl + Alt + F1), -log in, and change the directory to where dwm/slstatus is. We can run `make -install` to install the software and switch back to the graphical session -(Ctrl + Alt + F5). +these programs (in my case, using Mod + Shift + q). Then, switch to a tty +(Ctrl + Alt + F1), log in, and change the directory to where dwm/slstatus is. +We can run `make install` to install the software and switch back to the +graphical session (Ctrl + Alt + F5). The key combinations for switching to the tty and back may differ across systems. The ones listed above are for OpenBSD. @@ -86,5 +85,5 @@ q12vu Another old commit. 3fkdf Version 6.5. ``` -And finally, commit and push all the changes to my own git repository. +And finally, I commit and push all the changes to my git repository. |