| 5 |
<!ENTITY % default SYSTEM "default.ent"> %default; |
<!ENTITY % default SYSTEM "default.ent"> %default; |
| 6 |
|
|
| 7 |
]> |
]> |
| 8 |
<!-- CVS revision of this document "$Revision: 1.66 $" --> |
<!-- CVS revision of this document "$Revision: 1.67 $" --> |
| 9 |
<!-- CVS revision of original english document "*.**" --> |
<!-- CVS revision of original english document "*.**" --> |
| 10 |
|
|
| 11 |
<debiandoc> |
<debiandoc> |
| 1904 |
|
|
| 1905 |
<sect id="orig-tar">The <file>orig.tar.gz</file> file |
<sect id="orig-tar">The <file>orig.tar.gz</file> file |
| 1906 |
<p> |
<p> |
| 1907 |
If you simply copy contents of <file>debian/</file> directory from old |
If you simply copy the content of <file>debian/</file> directory from |
| 1908 |
package into new upstream version of source tree and try to build |
the old package into the new upstream version of the source tree and try |
| 1909 |
package, you may end up with unintended result of creating a native |
to build package, you may end up unintentionally creating a native |
| 1910 |
source package which comes without <file>diff.gz</file> file. This type |
source package which comes without <file>diff.gz</file> file. This type |
| 1911 |
of packaging is allowed for the packages made only for Debian. |
of packaging is only appropriate for the debian-specific packages, which |
| 1912 |
|
will never be useful in another distribution. |
| 1913 |
<footnote> |
<footnote> |
| 1914 |
Some people argue that, even for the Debian specific package, |
Some people argue that, even for the Debian specific package, it is a |
| 1915 |
it is a better practice to package the contents of <file>debian/</file> |
better practice to package the contents of the <file>debian/</file> |
| 1916 |
directory residing not in the <file>orig.tar.gz</file> file but in the |
directory residing not in the <file>orig.tar.gz</file> file, but in the |
| 1917 |
<file>diff.gz</file> file. |
<file>diff.gz</file> file. |
| 1918 |
</footnote> |
</footnote> |
| 1919 |
<p> |
<p> |
| 1920 |
Here, you must have the upstream tar ball as <file>orig.tar.gz</file> |
Here, you must have the upstream tarball as |
| 1921 |
file in the parent directory. Usually, this tar ball should untar to a |
<file><packagename>_<upstream_version>.orig.tar.gz</file> |
| 1922 |
source tree rooting from a directory with a name |
file in the parent directory. Usually, this tarball should untar to a |
| 1923 |
|
source tree under a directory name |
| 1924 |
<file><packagename>-<upstream_version>/</file>. In this |
<file><packagename>-<upstream_version>/</file>. In this |
| 1925 |
cases, <file>orig.tar.gz</file> source file can be obtained by simply |
cases, the <file>orig.tar.gz</file> source file can be obtained by |
| 1926 |
rename upstream tar ball to the original file name |
simply rename the upstream's release tarball to: |
| 1927 |
<file><packagename>_<upstream_version>.orig.tar.gz</file> . |
<file><packagename>_<upstream_version>.orig.tar.gz</file> . |
| 1928 |
Please note that the 2 changes exist between source tree directory name |
Please note that 2 changes exist between source tree directory name and |
| 1929 |
and the tar file name: |
the tar file name: |
| 1930 |
<list compact> |
<list compact> |
| 1931 |
<item>Change hyphen "<tt>-</tt>" to underscore "<tt>_</tt>" |
<item>Change hyphen "<tt>-</tt>" to underscore "<tt>_</tt>" |
| 1932 |
<item>Add "<tt>orig.</tt>" before "<tt>tar.gz.</tt>" |
<item>Add "<tt>orig.</tt>" before "<tt>tar.gz.</tt>" |