[10b] | DWM: Git Install & Patching

In this video I am installing DWM with Git and manage patches through it. I am not a Git expert, but it should be enough info to get you started. I hope you enjoy the video!
Suckless website: sukless.org
** Become a Patreon to support the channel: bit.ly/3dGGZxQ **
** Donate to the channel by visiting our Website **
My Hardware:
AMD Ryzen 9
32 GB RAM
Sapphire RX 5700 XT
My software:
Distro: Arch Linux
Video editing software: Kdenlive
Music: Jindupe by Lauren Duski
Check out our Website and connect on Social Media!
Website: ermannoferrari.net
Facebook: ermannoferraritechcoach
Instagram: efsoftwareandit
#howto #dwm #git

[@ipekposet8639]

DWM rocks, I was surprised by its speed and low resources consumption. And now thanks to you, I can fully customize it ! Time to fly 🛫 🛩️

[@JasonColdham]

Great video Sir! Can’t wait for the next one 👍🏻

[@zedrobot5864]

We would like to see u live sometimes best teacher ever ❤❤

[@eflinux]

Thanks! I’m planning to do that soon. I wanted to do it already since some time, but there’ve been many time constraints.

[@peterkruskopfs3626]

I now understand how to patch. Great video Ermanno!

[@eflinux]

My pleasure!

[@SamSam-df4xp]

As usual, excellent and to the point. I am not a fan of suckless utilities but I would love to see whenever possible, if or when you do a video on xmonad. 😉🙂🙂👍👍👍

[@eflinux]

I’ll definitely cover xmonad a little later.

[@user-gp9ln4wj1r]

Thanks a lot, thanks to you, I have once again returned to mastering git, and it looks like this attempt was successful!!!

[@harryvendryes]

Thanks :-) Perfect. Subscribed. You deserve more views.

[@eflinux]

Thanks for the sub!

[@NixwayRU]

Cool video! Thank you!

[@sebascm7278]

Never mind I solved my questions. Thanks

[@motif5775]

Great video!! So I assumed you left the git folder after installing dwm. If someone (me) deleted that git folder...would I be able to just init dwm dir? Would that work the same or does it have to be the git dir that came with dwm?

[@lesterknome]

Thanks for these awesome videos! Can you explain why installing this way might be better than using AUR? I understand the AUR may be more friendly with tracking files.

[@eflinux]

There are technical and philosophical reasons behind this. According to Suckless the software is supposed to be installed by compiling it from source. Technically speaking, installing from the AUR, you’ll not be able to profit from all features of the wm as you would if you compile and installed from source.

[@krozareq]

The AUR is effectively a collection of repositories of PKGBUILD scripts. PKGBUILD scripts are part of the Arch Build System that dictates the building of source code and packaging it into a filesystem tree, and then archived into a tarball. The resulting tarball from the build process can then be installed by pacman. You absolutely can install and maintain dwm as a package. But it makes no sense to do automatically from an AUR helper (such as yay). You can use your own PKGBUILD to build dwm and install it every time. look up Arch Wiki articles on "PKGBUILD" and "makepkg" for how this works. You can also retrieve the build repo (where the PKGBUILD is) for dwm by using the "-G" option i n your AUR helper. I.e. "yay -G dwm" or by git cloning the AUR repo "git clone aur.archlinux.org/dwm.git" and reviewing the PKGBUILD file that the AUR maintainer produced.

[@JasonColdham]

Ermanno, can you please explain how to get audio working with dwm. I assume it’s to do with the .xinitrc file?

[@eflinux]

Hi Jason, it’s coming up in the next video. You’ll need to install a few packages and create a few key bindings.

[@lmaolmao9337]

Hi, thanks for the video. When we enter our email and username where is that stored/ where does that go to?

[@nielsroetert]

Great video as always, regarding the $ git commit -m config, instead of config shouldn't that state what you changed, like $ git commit -m "Changed mod key to Win/Super key"?

[@eflinux]

Thanks Niels! The -m option is just a message, it can be anything you want. You can of course specify more details if you want to.

[@alphabennyrosy5068]

Btw when u do git merge, you don't need a message, it even ignores the - m. I have patched and edited git branches and I recompiled dwm so many times at this point that not writing -m with a message after every merge saved me so much time.

[@eflinux]

Hi there! I agree with you. If I'd do this everyday I definitely wouldn't do that neither. I showed it for the purpose of the tutorial, but as Niels pointed out, it could be more descriptive. Ermanno

[@treverkirk8110]

Why did you use ‘Make && Make Clean Install’ instead of just ‘Make Clean Install’, like you did on the previous DWM videos?

[@favreje]

I have the same question. I know this is a year old but can anyone provide some feedback?

[@zc0rp10]

Not sure if the new DWM video is already done. But if it's not completed yet it might be worthwhile to briefly touch on the @@ -1,5 +1,9 @@ applyrules(Client *x) lines in the .rej file means. Not having dealt with merging files before they had me confused for a while before some googling cleared it up. Also could be worth while to mention that the endings to the patches files, i.e "-6.2.diff", "-20200508-7b77734.diff" etc. refer to the version or git commit of the tool on which the patch can be applied correctly and is working with. Once I figured this out and stopped matching 6.2 patches with git commits that were after that, the amount of merging conflicts at patching went down to almost zero. Maybe you mentioned these things already and I just didn't pick up on it (I still hear new jokes every time i re-watch scrubs, and I've watched that series a million times over), but if not, I'm sure it could help some people out there suckless to.

[@eflinux]

Hi, thanks for the feedback. I'll add this to an eventual future video. The thing is sometimes you'll apply an older version of the patch and it'll still works as for the st terminal (coming up in the next video), but I totally get what you mean.

[@zc0rp10]

@@eflinux Yeah for sure, I think it's one of those things that get worse the more patches you keep adding onto it. With just one or two patches you're probably going to be alright even when they're out of version sync, but as you keep building on to it the risk of a merge conflict increases.

[@eflinux]

Exactly, that's why I don't apply too many patches to it.

Hi Ermanno! Can you create a new video about awesome wm? ;)

[@eflinux]

Hi Fabio! I definitely will in the future :)

@@eflinux Great!

[@theimmortalsinger3762]

How do I upload all that to github? Lovely video btw

[@eflinux]

You can check my GitLab video :)

[@davisbindejazz]

Why you always install xorg packages and edit xinitrc file? I guess you assume people are interested to do this on fresh install. But not always. In fact lot of newbies doesn't even know they already have xorg, xinit etc. Anyway, I enjoyed this video! Thanks!

[@eflinux]

Hi there! And thanks for the feedback. I normally tell people in the video to install a display manager or follow the install with xinit, whichever they feel more comfortable with. In this particular video I didn’t as I assumed with git people normally install via xinit. Thanks for watching!

[@marol75-l2h]

I wonder - is it really necessary to do all these operations? I remember the same fullgaps was installed in part "a". The difference is - now it's done by means of git, right? Aaaand - that's it? Simply complicated because of suckless philosophy? I'm sorry, but it suckmore. More time, energy (may be nerves...) :)

[@eflinux]

It’s not, it’s just a different approach if you want to use the git version.

[@anangelsdiaries]

honestly I kinda feel you. However the appeal of the git method is for when you are planning to play with multiple patches, since you can always clean your master and try different combinations basically with impunity (if you know what you are doing), for someone that is just planning to use 1 or 2 patches and never more this method is a bit overkill.