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
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
happy for DEBIAN
----------------------
This is a build of the CVS tree of happy. The CVS information is
intentionally left in the debianized source tree, so you can update from
this point, if you like.
hints on building
-----------------
* If you want to compile the source package yourself and the build process
fails without real reason, try to alter the memory values by tweaking
options like: `SRC_HC_OPTS += -H120m -optCrts-M120m' in `mk/build.mk'
(also have a look at `debian/patches/happy_build.dpatch')
hints on patching/updating
--------------------------
* Local patches are taken from debian/patches/*.dpatch. Another
reasonable strategy AFTER updating from CVS is:
$ debian/rules patch
<look for any errors>
$ debian/rules unpatch
<solve the errors from above (1)>
<repeat from first step until everything goes smooth>
Then build the package.
(1) normally, this just means removing the failed patch from the
debian/patches/ directory, as it probably has gone upstream, or is
solved by the upstream people in another way...
* If you want to do patches by yourself, I'd suggest, you do it like
this:
Edit the to-be-patched files directly in the directory tree.
Now you have two possibilities:
a) doing it via the "dpkg-buildpackage"-method:
Just build the package with `debuild' or friends. The changes
will be reflected in the *.diff.gz file.
b) doing it directly:
For every changed file (or set of files), diff it with the
original one (provided you made a backup copy before editing
:-)). Remember to make the diff relative to "<toplevel source
tree>/.."! For example:
$ diff -u happy-1.7/happy/Makefile.orig \
happy-1.7/happy/Makefile
or, when using the original tarball:
$ diff -u happy-1.7.orig/hslibs/Makefile \
happy-1.7/happy/Makefile
Put the diff in a file in debian/patches/, that ends with suffix
`.dpatch'. Then touch <source tree>/patch-<patched-file-name-with-suffix>
eg. for patch `debian/patches/happy_foopatch.dpatch':
$ touch patch-happy_foopatch.dpatch
You then can test the patch with
$ debian/rules unpatch
<the patch should get reverted smoothly>
$ debian/rules patch
<now all patches should be applied again without errors>
Instead of diffing the files by hand, you can also
i) perform step a)
ii) clean the build tree
iii) cut'n'paste the patch out of the *.diff.gz and put it into
debian/patches/.
Then carry on like before (i.e. test, whether it works), and
build a new package. The new *.diff.gz is pristine, if it only
contains files in the `debian/' directory (you can check the
diff.gz with `zgrep "^+++ " <diff.gz file>').
Michael Weber <michaelw@debian.org>, Sat, 26 Jun 1999 17:52:29 +0200
|
