File: Patch

package info (click to toggle)
afterstep 2.2.12-18.1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 33,184 kB
  • sloc: ansic: 201,695; sh: 5,894; xml: 3,721; makefile: 2,094; perl: 1,558; cpp: 811
file content (68 lines) | stat: -rw-r--r-- 2,094 bytes parent folder | download | duplicates (9)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
How can you make a patch ?

* Put the original AfterStep in some dir, let's say AfterStep-old/

* Put your new source tree in something like AfterStep-new/

* Then run :
diff -N -u -r AfterStep-old/ AfterStep-new/ > yourname-patch
gzip yourname-patch

* People will apply your patch by just running :
tar -zxvf AfterStep-old.tgz
gunzip yourname-patch.gz
patch -p0 < yourname-patch

Guylhem

-----------

Alternatively, you can use makeaspatch, makeasclean and makeasversion, included
in the tools dir of the AS distribution.  makeasclean cleans the AS source 
tree, and makeaspatch makes a patch.

* Put makeaspatch, makeasclean, makeasversion in your path
* Put the original AfterStep source in /usr/src/AfterStep/AfterStep-current
* Put your modified version in /usr/src/AfterStep/AfterStep-devel
* cd /usr/src/AfterStep/AfterStep-devel
* run makeasclean
* run makeasversion (with an argument for the patch number
  e.g. 'makeasversion 1.7.76')
* If there is a Makefile, now use 'make config'; otherwise run this:

  autoconf --localdir=autoconf autoconf/configure.in > \
  configure ; chmod 755 configure
  autoheader --localdir=autoconf autoconf/configure.in > \
  autoconf/config.h.in ; chmod 644 autoconf/config.h.in

* Run makeaspatch, which makes the patch as /tmp/patch
* Look at your patch and make sure there aren't any silly mistakes :)
* Check your patch by patching the original code, compiling, and testing
  cd /usr/src/AfterStep/AfterStep-current
  cat /tmp/patch | patch -p1
  # the next line is paranoia only - makeaspatch will have done this already
  makeasclean
  install.script
* gzip the patch
  gzip /tmp/patch
* Send it to the AS maintainers!

Ethan

-----------

To apply a patch (or patches), I find the following method easiest:

* download a version of AS, and the patches for that version, say 1.7.0 
  (so the patches will be named 1.7.0-xx-*)
* extract AS:
  tar xzf AfterStep-1.7.0.tar.gz
* apply the patches:
  cd AfterStep-1.7.0
  gzip -dc ../1.7.0-* | patch -p1

If the patches are not gzipped, change the last step to:

* cat ../1.7.0-* | patch -p1

Ethan