|
|
146.
|
|
|
diff and patch
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/introduction.xml:167(title)
|
|
|
147.
|
|
|
The <application>diff</application> program can be used to compare two files and to make patches. A typical example might be <application>diff -ruN file.old file.new > file.diff</application>. This command will create a diff (recursively if directories are used) that shows the changes, or <quote>delta</quote>, between the two files.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/introduction.xml:169(para)
|
|
|
148.
|
|
|
The <application>patch</application> program is used to apply a patch (usually created by <application>diff</application> or another similar program) to a file or directory. To apply the patch created above, we can invoke <application>patch -p0 < file.diff</application>. The <emphasis>-p</emphasis> tells <application>patch</application> how much it should strip from the paths for the file names in the patch. -p0 means to strip nothing, or leave the path intact.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/introduction.xml:175(para)
|
|
|
149.
|
|
|
Getting Started
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:15(title)
|
|
|
150.
|
|
|
Packaging Tools
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:18(title)
|
|
|
151.
|
|
|
There are many tools written specifically for packaging on Debian-based systems. Many of them are not <emphasis>essential</emphasis> to creating packages but are very helpful and often automate repetitive tasks. Their <application>man</application> and <application>info</application> pages are good sources of information. However, the following is a list of packages that are deemed necessary to begin packaging:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:20(para)
|
|
|
152.
|
|
|
build-essential
|
|
|
|
|
build-essential
|
|
Translated and reviewed by
Donnie Lomat
|
|
|
|
Located in
C/getting_started.xml:29(application)
|
|
|
153.
|
|
|
is a metapackage that depends on <application>libc6-dev</application>, <application>gcc</application>, <application>g++</application>, <application>make</application>, and <application>dpkg-dev</application>. One package that you might not be familiar with is <application>dpkg-dev</application>. It contains tools such as <application>dpkg-buildpackage</application> and <application>dpkg-source</application> that are used to create, unpack, and build source and binary packages.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:30(para)
|
|
|
154.
|
|
|
devscripts
|
|
|
|
|
devscripts
|
|
Translated and reviewed by
Donnie Lomat
|
|
|
|
Located in
C/getting_started.xml:43(application)
|
|
|
155.
|
|
|
contains many scripts that make the packager's maintenance work much easier. Some of the more commonly used are <application>debdiff</application>, <application>dch</application>, <application>debuild</application>, and <application>debsign</application>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:44(para)
|
