|
Lines 635-645
Link Here
|
| 635 |
<replaceable>*</replaceable> indicates |
635 |
<replaceable>*</replaceable> indicates |
| 636 |
the pathnames of the files that are patched, |
636 |
the pathnames of the files that are patched, |
| 637 |
such as <filename>patch-Imakefile</filename> or |
637 |
such as <filename>patch-Imakefile</filename> or |
| 638 |
<filename>patch-src-config.h</filename>. These files should |
638 |
<filename>patch-src::config.h</filename>. All patches must be |
|
|
639 |
relative to <makevar>WRKSRC</makevar> (generally the directory your |
| 640 |
port's tarball unpacks itself into, that being where the build is |
| 641 |
done), and the / signs must be substituted with :: in this relative |
| 642 |
path when constructing patch filenames, as the example represents |
| 643 |
above. The patch files should |
| 639 |
be stored in <makevar>PATCHDIR</makevar>, from where they will be |
644 |
be stored in <makevar>PATCHDIR</makevar>, from where they will be |
| 640 |
automatically applied. All patches must be relative to |
645 |
automatically applied. |
| 641 |
<makevar>WRKSRC</makevar> (generally the directory your port's |
|
|
| 642 |
tarball unpacks itself into, that being where the build is done). |
| 643 |
To make fixes and upgrades easier, you should avoid having more than |
646 |
To make fixes and upgrades easier, you should avoid having more than |
| 644 |
one patch fix the same file (e.g., <filename>patch-file</filename> and |
647 |
one patch fix the same file (e.g., <filename>patch-file</filename> and |
| 645 |
<filename>patch-file2</filename> both changing |
648 |
<filename>patch-file2</filename> both changing |