Bug#561952: developers-reference: Section 4.6.3 - please document new source package formats "3.0 (quilt)" and "3.0 (native)"
Tommi Vainikainen
Severity: normal
Tags: patch
Please document the new source package formats "3.0 (native)" and "3.0
(quilt)"[1] in the section 4.6.3 Packages of the Debian Developer's
Reference.
Following patch might be helpful.
Charles Plessy
> Package: developers-reference
> Severity: normal
> Tags: patch
>
> Please document the new source package formats "3.0 (native)" and "3.0
> (quilt)"[1] in the section 4.6.3 Packages of the Debian Developer's
> Reference.
Dear Tommi and all,
there is at least one more place that would desserve an update, the
section 6.7.8.
Here is a draft patch, which probably requires more editing:
Index: best-pkging-practices.dbk
===================================================================
--- best-pkging-practices.dbk (révision 7003)
+++ best-pkging-practices.dbk (copie de travail)
@@ -1798,11 +1812,11 @@
<title>Changing binary files in <literal>diff.gz</literal></title>
<para>
Sometimes it is necessary to change binary files contained in the original
-tarball, or to add binary files that are not in it. If this is done by simply
-copying the files into the debianized source tree,
-<command>dpkg-source</command> will not be able to handle this. On the other
-hand, according to the guidelines given above, you cannot include such a
-changed binary file in a repackaged <filename>orig.tar.gz</filename>. Instead,
+tarball, or to add binary files that are not in it. According to the guidelines
+given above, binary files should not be changed in a repackaged
+<filename>orig.tar.gz</filename>. Changes can be done by simply
+copying the files into the debianized source tree. <command>dpkg-source</command>
+handles this for source formats 3.0. For source formats lower than 2.0,
include the file in the <filename>debian</filename> directory in
<command>uuencode</command>d (or similar) form <footnote><para> The file should
have a name that makes it clear which binary file it encodes. Usually, some
I have not checked other parts of the Developers Reference if they need update.
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Raphael Hertzog
thanks
On Mon, 21 Dec 2009, Tommi Vainikainen wrote:
> Please document the new source package formats "3.0 (native)" and "3.0
> (quilt)"[1] in the section 4.6.3 Packages of the Debian Developer's
> Reference.
Right, thanks for the reminder. I did not use your patch. You'll find
attached the patch that I committed. Please review and do not hesitate to
spot mistakes.
I used *.{gz,bz2,lzma} when describing the source format but used
only *.{gz,bz2} in samples and generic explanations since those extensions
are only allowed on ftp-master.
Cheers,
--
Raphaël Hertzog
Tommi Vainikainen
> Right, thanks for the reminder. I did not use your patch. You'll find
> attached the patch that I committed. Please review and do not hesitate to
> spot mistakes.
Looks good, but there was one spelling mistake "muliple" (multiple) in
the section 4.6.3 in the attached patch.
--
Tommi Vainikainen
Raphael Hertzog
> Raphael Hertzog <her...@debian.org> writes:
> > Right, thanks for the reminder. I did not use your patch. You'll find
> > attached the patch that I committed. Please review and do not hesitate to
> > spot mistakes.
>
> Looks good, but there was one spelling mistake "muliple" (multiple) in
> the section 4.6.3 in the attached patch.
Thanks, fixed.
Cheers,
--
Raphaël Hertzog