2002-04-19 19:27:01 +01:00
|
|
|
<sect2><title>Contents of Patch-&patch-contversion;</title>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
<sect3><title>Program Files</title>
|
|
|
|
<para>patch</para></sect3>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
<sect3><title>Descriptions</title>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
<sect4><title>patch</title>
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>The patch program modifies a file according to a patch file. A patch
|
2001-01-24 00:31:17 +00:00
|
|
|
file usually is a list created by the diff program that contains
|
|
|
|
instructions on how an original file needs to be modified. Patch is used
|
|
|
|
a lot for source code patches since it saves time and space. Imagine
|
2002-05-26 22:25:09 +01:00
|
|
|
a package that is 1 MB in size. The next version of that package
|
2001-03-16 18:09:38 +00:00
|
|
|
only has changes in two files of the first version. It can be shipped as an
|
2002-05-26 22:25:09 +01:00
|
|
|
entirely new package of 1 MB or just as a patch file of 1 KB which will
|
2001-01-24 00:31:17 +00:00
|
|
|
update the first version to make it identical to the second version. So
|
2001-03-16 18:09:38 +00:00
|
|
|
if the first version was downloaded already, a patch file avoids
|
2002-02-06 23:15:46 +00:00
|
|
|
a second large download.</para></sect4>
|
|
|
|
|
|
|
|
</sect3>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|