2

DWM - how do you apply patches with patch?

view full story
linux-howto

https://bbs.archlinux.org – The patch file and the source files that the patch modifies should be in same directory. For dwm, I have found that installing via AUR is more trouble than it's worth. I have the source files of dwm in $HOME and just run make clean install inside this directory whenever I modify my config.h iTwenty https://bbs.archlinux.org/profile.php?id=43530 2011-12-06T15:05:54Z (HowTos)

Songlist's picture
Submitted by Songlist on 12/06/2011 – Made popular on 12/06/2011

Stories similar to DWM - how do you apply patches with patch?

vheon wrote:So you first patch the code with one patch and then apply the second one by hand and recreate the patch just for that caseSuch is the nature of patching dwm.I recently moved to using mercurial queues and guards - this, combined with keeping the number of patches down*, is the most effective approach I have found.For creating a new feature patch, diff against stable and send to the suck

Save the above to a file where your PKGBUILD file is. We'll call it uzbl.patch. Then cd to that directory and run "patch -p1 < uzbl.patch"Don't see why that wouldn't work (to patch the file I mean).

dodo3773 https://bbs.archlinux.org/profile.php?id=47076

2012-09-11T05:36:55Z

diff/patch a directory? 3 years 31 weeks ago

I can create a patch for a file with the following:

Code: diff -uN OldFile NewFile > patch.txt then apply the patch with:

Code: patch OldFile < patch.txt I tried this with directories:

Code: diff -uN OldDirectory NewDirectory > patch.txt it seemed to work fine. Then I tried to apply the patch:

Dwm 5.9 Compilation issues 1 year 35 weeks ago

The diff you use rename tile() to ntile(), you should not have tile in your config.h. The rest of errors probably relate to what the diff has nerfed.I think you should stay on 5.8.2 until all the patches have support for 5.9 if you can't patch on patch on your own.

livibetter https://bbs.archlinux.org/profile.php?id=16513

2011-09-12T14:49:19Z

tomd123 wrote:I figured out a way to avoid the segfault, you will have to rebuild vim from abs and apply the following patch to the PKGBUILD:https://gist.github.com/2423572I'm guessing this has something to do with arch's and vim's buildflags somehow not playing well together.This works with patch 496 and fixes python 3 support for me.  Thanks a lot.

saline https://bbs

how to update the patch files. 3 years 21 weeks ago

Hi guys,

I have question about patches. I have source tree and I have develop my own patch changing few files from the source tree. Now new version of the source tree arives and I want to apply my own old patches on the new source tree. Some of the files I am patching however are changed in the new source tree release.

As I replied to dodo3773's e-mail - I don't see reason to not apply patch from the official bugtracker, if it can fix serious or annoying bug.

Barthalion https://bbs.archlinux.org/profile.php?id=34421

2012-05-12T08:10:59Z

removing patch 16 weeks 4 days ago

of course. comment out the line where the patch is applied and rebuild.

Scimmia https://bbs.archlinux.org/profile.php?id=63385

2013-01-23T08:00:25Z

Because of the way the PKGBUILD is written.cat "$srcdir/"*.patch | patch -Np1Old patches in $srcdir will be applied if you haven't cleaned them out.

falconindy https://bbs.archlinux.org/profile.php?id=30251

2012-07-01T01:17:19Z