/[ddp]/manuals/trunk/maint-guide/maint-guide.en.dbk

Diff of /manuals/trunk/maint-guide/maint-guide.en.dbk

Parent Directory | Revision Log | View Patch Patch

-revision 8654 by osamu,
Sun Apr 10 09:13:27 2011 UTC
+revision 8705 by osamu,
Thu Apr 21 16:17:04 2011 UTC
 Line 29 
 for people to check official documentati
  <title>Debian New Maintainers' Guide</title>
  <bookinfo>
  <authorgroup>
- <author> <personname> <firstname>Josip</firstname> <surname>Rodin</surname> </personname> <email>joy-mg@debian.org</email> <contrib>(original contents)</contrib> </author>
+ <!-- do not use firstname and surname tags it braks Japanese.  The same with othercredit -->
- <author> <personname> <firstname>Osamu</firstname> <surname>Aoki</surname> </personname> <email>osamu@debian.org</email> <contrib>(updated contents)</contrib> </author>
+ <author> <personname>Josip Rodin</personname> <email>joy-mg@debian.org</email> <contrib>original contents</contrib> </author>
+ <author> <personname>Osamu Aoki</personname> <email>osamu@debian.org</email> <contrib>updated contents</contrib> </author>
  <!-- translator credits in po4a/translator.*.ent -->
  &othercredit;
  </authorgroup>
-Line 66 
 The New-Maintainer's Debian Packaging Ho
+Line 67 
 The New-Maintainer's Debian Packaging Ho
  </bookinfo>
  <chapter id="start"><title>Getting started The Right Way</title>
  <para>
- This document tries to describe building of a Debian package to the common
+ This document tries to describe the building of a Debian package to ordinary
- Debian user, and the prospectus developer.  It uses pretty common language, and
+ Debian users and prospective developers.  It uses fairly non-technical language, and
- it's well covered with working examples.  There is an old Roman saying,
+ it's well covered with working examples.  There is an old Latin saying:
- <emphasis>Longum iter est per preaecepta, breve et efficax per
+ <emphasis>Longum iter est per praecepta, breve et efficax per
- exempla!</emphasis> (It's a long way by the rules, but short and efficient with
+ exempla</emphasis> (It's a long way by the rules, but short and efficient with
- examples!).
+ examples).
  </para>
  <para>
  This document has been updated for the Debian <literal>&base-release;</literal>
  release.
- <footnote><para> The document assumes you are using the
+ <footnote><para> The document assumes you are using a
- <literal>&base-release;</literal> system or newer.  If you need to follow this
+ <literal>&base-release;</literal> or newer system.  If you need to follow this
- text in the older system (including the older Ubuntu system etc.), you must
+ text in an older system (including an older Ubuntu system etc.), you must
  install backported <systemitem role="package">dpkg</systemitem> and
  <systemitem role="package">debhelper</systemitem> packages, at least.
  </para> </footnote>
-Line 87 
 install backported <systemitem role="pac
+Line 88 
 install backported <systemitem role="pac
  One of the things that makes Debian such a top-notch distribution is its
  package system.  While there is a vast quantity of software already in the
  Debian format, sometimes you need to install software that isn't.  You may be
- wondering how you can make your own packages and perhaps you think it is a very
+ wondering how you can make your own packages; and perhaps you think it is a very
  difficult task.  Well, if you are a real novice on Linux, it is hard, but if
- you were rookie, you wouldn't be reading this doc now.  :-) You do need to know
+ you were a rookie, you wouldn't be reading this document now&nbsp;:-)
- a little about Unix programming but you certainly don't need to be a wizard.
+ You do need to know a little about Unix programming but you certainly
+ don't need to be a wizard.
  <footnote><para>
- You can learn basic operations of the Debian system from
+ You can learn about the basic handling of a Debian system from the
  <ulink url="&debref;">Debian Reference</ulink>.  It contains some pointers to
  learn about Unix programming, too.
  </para></footnote>
  </para>
  <para>
  One thing is certain, though: to properly create and maintain Debian packages
- you need many hours.  Make no mistake, for our system to work the maintainers
+ takes many hours.  Make no mistake, for our system to work the maintainers
  need to be both technically competent and diligent.
  </para>
  <para>
  This document will explain every little (at first maybe irrelevant) step, and
  help you create that first package, and to gain some experience in building
- next releases of that and maybe other packages later on.
+ the next releases of that and maybe other packages later on.
  </para>
  <para>
- If you need some help on packaging, please read <xref linkend="helpme"/> .
+ If you need some help on packaging, please read <xref linkend="helpme"/>.
  </para>
  <para>
  Newer versions of this document should always be available online at
  <ulink url="&maint-guide;"/> and in the
  <systemitem role="package">maint-guide</systemitem> package.
  The translations may be available in packages such as
  <systemitem role="package">maint-guide-es</systemitem>.
+ Please note that this documentation may be slightly outdated.
  </para>
- <section id="socialdynamism"><title>Social dynamism of Debian</title>
+ <section id="socialdynamism"><title>Social dynamics of Debian</title>
  <para>
- Here are my observation of the social dynamism of Debian.
+ Here are some observations of Debian's social dynamics, presented in the hope
+ that it will prepare you for interactions with Debian.
  </para>
  <itemizedlist>
  <listitem><para>We all are volunteers.</para>
      <itemizedlist>
-     <listitem><para>You can not impose others what to do.</para></listitem>
+     <listitem><para>You cannot impose on others what to do.</para></listitem>
      <listitem><para>You should be motivated to do things by yourself.</para></listitem>
      </itemizedlist></listitem>
  <listitem><para>Friendly cooperation is the driving force.</para>
-Line 135 
 Here are my observation of the social dy
+Line 139 
 Here are my observation of the social dy
  <listitem><para>Debian is not your school where you get automatic attention of teachers.</para>
      <itemizedlist>
      <listitem><para>You should be able to learn many things by yourself.</para></listitem>
-     <listitem><para>Attention of other volunteers is the very scarce resource.</para></listitem>
+     <listitem><para>Attention from other volunteers is a very scarce resource.</para></listitem>
      </itemizedlist></listitem>
  <listitem><para>Debian is constantly improving.</para>
      <itemizedlist>
-     <listitem><para>You should adapt yourself to changes.</para></listitem>
+     <listitem><para>You are expected to make high quality packages.</para></listitem>
-     <listitem><para>Documentation may be slightly outdated .</para></listitem>
+     <listitem><para>You should adapt yourself to change.</para></listitem>
      </itemizedlist></listitem>
  </itemizedlist>
  <para>
- Since we focus only on technical aspects of packaging in this document,
+ There are several types of people interacting around Debian with different
- please refer to the following to learn how Debian functions and how you can get involved.
+ roles.
  </para>
  <itemizedlist>
- <listitem><para><ulink url="&logiciellibre;">Debian: 17 ans de logiciel libre,  "do-ocracy" et démocratie</ulink> (Introductory slides in English PDF) </para> </listitem>
+ <listitem>
- <listitem><para><ulink url="&nm-do;">Debian New Maintainer site</ulink> (official) </para> </listitem>
+ <para>
- <listitem><para><ulink url="&debianmentorfaq;">Debian Mentors FAQ</ulink> (supplemental) </para> </listitem>
+ <emphasis role="strong">upstream author</emphasis>: the person who made the
+ original program.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="strong">upstream maintainer</emphasis>: the person who
+ currently maintains the program.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="strong">maintainer</emphasis>: the person making the Debian
+ package of the program.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="strong">sponsor</emphasis>: a person who helps maintainers to
+ upload packages to the official Debian package archive (after checking their
+ contents).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="strong">mentor</emphasis>: a person who helps novice
+ maintainers with packaging etc.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="strong">Debian Developer</emphasis> (DD): a member of
+ the Debian project with full upload rights to the official Debian package
+ archive.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="strong">Debian Maintainer</emphasis> (DM): a person with
+ limited upload rights to the official Debian package archive.
+ </para>
+ </listitem>
  </itemizedlist>
- </section>
- <section id="debiandeveloper"><title>Official Debian Developer</title>
  <para>
- You can not become an official
+ Please note that you cannot become an official
- <emphasis role="strong">Debian Developer</emphasis> (DD) over night because it
+ <emphasis role="strong">Debian Developer</emphasis> (DD) overnight, because it
  takes more than technical skill.  Please do not be discouraged by this.  If it
  is useful to others, you can still upload your package either as a
  <emphasis role="strong">maintainer</emphasis> through a
-Line 166 
 is useful to others, you can still uploa
+Line 209 
 is useful to others, you can still uploa
  <para>
  Please note that you do not need to create any new package to become an
  official Debian Developer.  Contributing to the existing packages can provide a
- path to become an official Debian Developer too.  There are many packages
+ path to becoming an official Debian Developer too.  There are many packages
- waiting for good maintainers (see <xref linkend="choose"/> ).
+ waiting for good maintainers (see <xref linkend="choose"/>).
+ </para>
+ <para>
+ Since we focus only on technical aspects of packaging in this document,
+ please refer to the following to learn how Debian functions and how you can get involved.
  </para>
+ <itemizedlist>
+ <listitem><para><ulink url="&logiciellibre;">Debian: 17 years of Free Software, "do-ocracy", and democracy</ulink> (Introductory slides) </para> </listitem>
+ <listitem><para><ulink url="&debianorghelp;">How can you help Debian?</ulink> (official) </para> </listitem>
+ <listitem><para><ulink url="&debianfaqhelp;">The Debian GNU/Linux FAQ, Chapter 13 - 'Contributing to the Debian Project'</ulink> (semi-official) </para> </listitem>
+ <listitem><para><ulink url="&debianwikihelp;">Debian Wiki, HelpDebian</ulink> (supplemental) </para> </listitem>
+ <listitem><para><ulink url="&nm-do;">Debian New Maintainer site</ulink> (official) </para> </listitem>
+ <listitem><para><ulink url="&debianmentorfaq;">Debian Mentors FAQ</ulink> (supplemental) </para> </listitem>
+ </itemizedlist>
  </section>
  <section id="needprogs"><title>Programs you need for development</title>
  <para>
-Line 187 
 or with <literal>dpkg -s <replaceable>pa
+Line 242 
 or with <literal>dpkg -s <replaceable>pa
  <para>
  The most important package to install on your development system is the
  <systemitem role="package">build-essential</systemitem> package.  Once you try
- to install it, it will <emphasis>pull in</emphasis> other packages required to
+ to install that, it will <emphasis>pull in</emphasis> other packages required to
  have a basic build environment.
  </para>
  <para>
- For some types of packages, that is all you will require, however there is
+ For some types of packages, that is all you will require; however, there is
  another set of packages that while not essential for all package builds are
- useful to have install or may be required by your package:
+ useful to have installed or may be required by your package:
  </para>
  <itemizedlist>
  <listitem>
  <para>
- <systemitem role="package">file</systemitem> - this handy program can determine
+ <systemitem role="package">autoconf</systemitem>, <systemitem
- what type a file is.  (see <citerefentry> <refentrytitle>file</refentrytitle>
+ role="package">automake</systemitem>, and <systemitem
- <manvolnum>1</manvolnum> </citerefentry>)
+ role="package">autotools-dev</systemitem> - many newer programs use configure
- </para>
+ scripts and <filename>Makefile</filename> files preprocessed with the help of
- </listitem>
+ programs like these (see <literal>info autoconf</literal>, <literal>info
- <listitem>
+ automake</literal>).  <systemitem role="package">autotools-dev</systemitem>
- <para>
+ keeps up-to-date versions of certain auto files and has documentation about the
- <systemitem role="package">patch</systemitem> - this very useful utility will
+ best way to use those files.
- take a file containing a difference listing (produced by the
- <command>diff</command> program) and apply it to the original file, producing a
- patched version.  (see <citerefentry> <refentrytitle>patch</refentrytitle>
- <manvolnum>1</manvolnum> </citerefentry>)
  </para>
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">perl</systemitem> - Perl is one of the most used
+ <systemitem role="package">debhelper</systemitem> and
- interpreted scripting languages on today's Unix-like systems, often referred to
+ <systemitem role="package">dh-make</systemitem> -
- as Unix's Swiss Army Chainsaw.  (see <citerefentry>
+ <systemitem role="package">dh-make</systemitem> is necessary to create
- <refentrytitle>perl</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>)
+ the skeleton of our example package, and it will use some of the
+ <systemitem role="package">debhelper</systemitem> tools for creating
+ packages.  They are not essential for this purpose, but are
+ <emphasis>highly</emphasis> recommended for new maintainers.  It makes
+ the whole process very much easier to start, and to control afterwards.
+ (See <citerefentry> <refentrytitle>dh_make</refentrytitle>
+ <manvolnum>1</manvolnum> </citerefentry>, <citerefentry>
+ <refentrytitle>debhelper</refentrytitle> <manvolnum>1</manvolnum>
+ </citerefentry>.) <footnote><para> There are also some more specialized
+ but similar packages such as
+ <systemitem role="package">dh-make-perl</systemitem>,
+ <systemitem role="package">dh-make-php</systemitem>, etc.  </para>
+ </footnote>
  </para>
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">python</systemitem> - Python is another of the most
+ <systemitem role="package">devscripts</systemitem> - this package contains some
- used interpreted scripting languages on the Debian system that combines
+ useful scripts that can be helpful for maintainers, but they are also
- remarkable power with very clear syntax.  (see <citerefentry>
+ not necessary for building packages.  Packages recommended and suggested
- <refentrytitle>python</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>)
+ by this package are worth looking into.  (See <ulink url="&devscripts-readme;"/>.)
  </para>
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">autoconf</systemitem>, <systemitem role="package">automake</systemitem> and <systemitem role="package">autotools-dev</systemitem> - many newer programs use configure
+ <systemitem role="package">fakeroot</systemitem> - this utility lets you
- scripts and <filename>Makefile</filename> files preprocessed with help of
+ emulate being root which is necessary for some parts of the build process.
- programs like these.  (see <literal>info autoconf</literal>, <literal>info
+ (See <citerefentry> <refentrytitle>fakeroot</refentrytitle>
- automake</literal>).  The <systemitem role="package">autotools-dev</systemitem>
+ <manvolnum>1</manvolnum> </citerefentry>.)
- keeps up-to-date versions of certain auto files and has documentation about the
- best way to use those files.
  </para>
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">dh-make</systemitem> and <systemitem role="package">debhelper</systemitem> - <systemitem role="package">dh-make</systemitem> is necessary to create the skeleton of our
+ <systemitem role="package">file</systemitem> - this handy program can determine
- example package, and it will use some of the <systemitem role="package">debhelper</systemitem> tools for creating packages.  They are
+ what type a file is.  (See <citerefentry> <refentrytitle>file</refentrytitle>
- not essential for creation of packages, but are <emphasis>highly</emphasis>
+ <manvolnum>1</manvolnum> </citerefentry>.)
- recommended for new maintainers.  It makes the whole process very much easier
- to start, and control afterwards.  (see <citerefentry>
- <refentrytitle>dh_make</refentrytitle> <manvolnum>1</manvolnum>
- </citerefentry>, <citerefentry> <refentrytitle>debhelper</refentrytitle>
- <manvolnum>1</manvolnum> </citerefentry>) <footnote><para> There
- are few similar but specialized packages such as <systemitem role="package">dh-make-perl</systemitem>, <systemitem role="package">dh-make-php</systemitem>, etc.  </para> </footnote>
  </para>
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">devscripts</systemitem> - this package contains some
+ <systemitem role="package">gfortran</systemitem> - the GNU Fortran 95 compiler,
- nice and useful scripts that can be helpful to the maintainers, but they are
+ necessary if your program is written in Fortran.  (See <citerefentry>
- also not necessary for building packages.  Packages recommended and suggested
+ <refentrytitle>gfortran</refentrytitle> <manvolnum>1</manvolnum>
- by this package are worth looking into.  (see
+ </citerefentry>.)
- <ulink url="&devscripts-readme;"/>.)
  </para>
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">fakeroot</systemitem> - this utility lets you
+ <systemitem role="package">git</systemitem> - this package provides a popular
- emulate being root which is necessary for some parts of the build process.
+ version control system designed to handle very large projects with speed and
- (see <citerefentry> <refentrytitle>fakeroot</refentrytitle>
+ efficiency; it is used for many high profile open source projects, most notably
- <manvolnum>1</manvolnum> </citerefentry>)
+ the Linux kernel.  (See <citerefentry> <refentrytitle>git</refentrytitle>
+ <manvolnum>1</manvolnum> </citerefentry>,
+ <ulink url="&git-doc;">git Manual</ulink>.)
  </para>
  </listitem>
  <listitem>
-Line 273 
 emulate being root which is necessary fo
+Line 329 
 emulate being root which is necessary fo
  <systemitem role="package">gnupg</systemitem> - a tool that enables you to
  digitally <emphasis>sign</emphasis> packages.  This is especially important if
  you want to distribute it to other people, and you will certainly be doing that
- when your work gets included in the Debian distribution.  (see <citerefentry>
+ when your work gets included in the Debian distribution.  (See <citerefentry>
- <refentrytitle>gpg</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>)
+ <refentrytitle>gpg</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>.)
- </para>
- </listitem>
- <listitem>
- <para>
- <systemitem role="package">gfortran</systemitem> - the GNU Fortran 95 compiler,
- necessary if your program is written in Fortran.  (see <citerefentry>
- <refentrytitle>gfortran</refentrytitle> <manvolnum>1</manvolnum>
- </citerefentry>)
  </para>
  </listitem>
  <listitem>
-Line 290 
 necessary if your program is written in
+Line 338 
 necessary if your program is written in
  <systemitem role="package">gpc</systemitem> - the GNU Pascal compiler,
  necessary if your program is written in Pascal.  Worthy of note here is
  <systemitem role="package">fp-compiler</systemitem>, the Free Pascal Compiler,
- which is also good at this task.  (see <citerefentry>
+ which is also good at this task.  (See <citerefentry>
  <refentrytitle>gpc</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>,
- <citerefentry> <refentrytitle>ppc386</refentrytitle> <manvolnum>1</manvolnum>
+ <citerefentry> <refentrytitle>ppc386</refentrytitle>
- </citerefentry>)
+ <manvolnum>1</manvolnum> </citerefentry>.)
  </para>
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">xutils-dev</systemitem> - some programs, usually
+ <systemitem role="package">lintian</systemitem> - this is the Debian package
- those made for X11, also use these programs to generate
+ checker, which can let you know of any common mistakes after you build the
- <filename>Makefile</filename> files from sets of macro functions.  (see
+ package, and explains the errors found.  (See <citerefentry>
- <citerefentry> <refentrytitle>imake</refentrytitle> <manvolnum>1</manvolnum>
+ <refentrytitle>lintian</refentrytitle> <manvolnum>1</manvolnum>
- </citerefentry>, <citerefentry> <refentrytitle>xmkmf</refentrytitle>
+ </citerefentry>,
- <manvolnum>1</manvolnum> </citerefentry>)
+ <ulink url="&lintian-doc;">Lintian User's Manual</ulink>.)
  </para>
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">lintian</systemitem> - this is the Debian package
+ <systemitem role="package">patch</systemitem> - this very useful utility will
- checker that can let you know of any common mistakes after you build the
+ take a file containing a difference listing (produced by the
- package, and explains the errors found.  (see <citerefentry>
+ <command>diff</command> program) and apply it to the original file, producing a
- <refentrytitle>lintian</refentrytitle> <manvolnum>1</manvolnum>
+ patched version.  (See <citerefentry> <refentrytitle>patch</refentrytitle>
- </citerefentry>,
+ <manvolnum>1</manvolnum> </citerefentry>.)
- <ulink url="&lintian-doc;">Lintian User's Manual</ulink>)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem role="package">patchutils</systemitem> - this package contains some
+ utilities to work with patches such as the <command>lsdiff</command>,
+ <command>interdiff</command> and <command>filterdiff</command> commands.
  </para>
  </listitem>
  <listitem>
-Line 330 
 Build From Source) bugs.  (see <citerefe
+Line 384 
 Build From Source) bugs.  (see <citerefe
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">patchutils</systemitem> - this package contains some
+ <systemitem role="package">perl</systemitem> - Perl is one of the most used
- utilities to work with patches such as the <command>lsdiff</command>,
+ interpreted scripting languages on today's Unix-like systems, often referred to
- <command>interdiff</command> and <command>filterdiff</command> commands.
+ as Unix's Swiss Army Chainsaw. (See <citerefentry>
+ <refentrytitle>perl</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>.)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem role="package">python</systemitem> - Python is another of the most
+ used interpreted scripting languages on the Debian system, combining
+ remarkable power with very clear syntax. (See <citerefentry>
+ <refentrytitle>python</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>.)
  </para>
  </listitem>
  <listitem>
  <para>
  <systemitem role="package">quilt</systemitem> - this package helps you to
- manage a series of patches by keeping track of the changes each of them makes.
+ manage large numbers of patches by keeping track of the changes each patch
- They are logically organized as a stack, and you can apply (=push), un-apply
+ makes. Patches can be applied, un-applied, refreshed, and more.  (See
- (=pop), refresh them easily by traveling into the stack.  (see <citerefentry>
+ <citerefentry> <refentrytitle>quilt</refentrytitle> <manvolnum>1</manvolnum></citerefentry>,
- <refentrytitle>quilt</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>,
+ <ulink url="&quilt-pdf;">quilt.pdf</ulink>.)
- <ulink url="&quilt-pdf;">quilt.pdf</ulink>)
  </para>
  </listitem>
  <listitem>
  <para>
- <systemitem role="package">git</systemitem> - this package provides popular
+ <systemitem role="package">xutils-dev</systemitem> - some programs, usually
- version control system designed to handle very large projects with speed and
+ those made for X11, also use these programs to generate
- efficiency; it is used for many high profile open source projects, most notably
+ <filename>Makefile</filename> files from sets of macro functions.  (See
- the Linux kernel.  (see <citerefentry> <refentrytitle>git</refentrytitle>
+ <citerefentry> <refentrytitle>imake</refentrytitle> <manvolnum>1</manvolnum>
- <manvolnum>1</manvolnum> </citerefentry>,
+ </citerefentry>, <citerefentry> <refentrytitle>xmkmf</refentrytitle>
- <ulink url="&git-doc;">git Manual</ulink>)
+ <manvolnum>1</manvolnum> </citerefentry>.)
  </para>
  </listitem>
  </itemizedlist>
-Line 363 
 of each program, at least, for the stand
+Line 425 
 of each program, at least, for the stand
  going now, but later on you'll be <emphasis>very</emphasis> glad you read it.
  </para>
  <para>
- If you have specific questions later, I suggest you to read the documents
+ If you have specific questions later, I would suggest re-reading the documents
- mentioned above again.  Since this is a tutorial, I intentionally skipped
+ mentioned above.  Since this is a tutorial, I have intentionally skipped
  details and provided only pointers to keep it simple.
  </para>
  </section>
- <section id="needdocs"><title>Documentations you need for development</title>
+ <section id="needdocs"><title>Documentation needed for development</title>
  <para>
  The following is the <emphasis>very important</emphasis> documentation which
  you should read along with this document:
-Line 376 
 you should read along with this document
+Line 438 
 you should read along with this document
  <itemizedlist>
  <listitem>
  <para>
+ <ulink url="&autotools-tutorial;">Autotools
+ Tutorial</ulink> provides a very good tutorial for <ulink url="&gnu-build-system;">the GNU Build System known
+ as the GNU Autotools</ulink> whose most important components are Autoconf,
+ Automake, Libtool, and gettext.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
  <systemitem role="package">debian-policy</systemitem> - the <ulink url="&debian-policy;">Debian Policy
  Manual</ulink> includes explanations of the structure and contents of the
  Debian archive, several OS design issues, the <ulink url="&fhs;">Filesystem Hierarchy Standard</ulink>
- (FHS, which says where each file and directory should be) etc.  For you, the most
+ (FHS, which says where each file and directory should be), etc.  For you, the most
  important thing is that it describes requirements that each package must
  satisfy to be included in the distribution (see the local copies of
  <ulink url="&policy-pdf;">policy.pdf</ulink> and <ulink url="&fhs-pdf;">fhs-2.3.pdf</ulink>).
-Line 391 
 satisfy to be included in the distributi
+Line 461 
 satisfy to be included in the distributi
  - the <ulink url="&developers-reference;">Debian Developer's Reference</ulink>
  describes all matters not specifically about the technical
  details of packaging, like the structure of the archive, how to rename, orphan,
- pick up packages, how to do NMUs, how to manage bugs, best packaging practices,
+ or adopt packages, how to do NMUs, how to manage bugs, best packaging practices,
- when and where to upload etc.  (see the local copy of
+ when and where to upload etc.  (See the local copy of
- <ulink url="&developers-refpdf;">developers-reference.pdf</ulink>).
+ <ulink url="&developers-refpdf;">developers-reference.pdf</ulink>.)
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="&autotools-tutorial;">Autotools
- Tutorial</ulink> provides very good tutorial for <ulink url="&gnu-build-system;">the GNU Build System known
- as the GNU Autotools</ulink> whose most important components are Autoconf,
- Automake, Libtool, and gettext.
  </para>
  </listitem>
  <listitem>
-Line 411 
 two pieces of documentation from the GNU
+Line 473 
 two pieces of documentation from the GNU
  <ulink url="&gnu-standard;">GNU Coding Standards</ulink>, and
  <ulink url="&gnu-maintainer;">Information for Maintainers of GNU Software</ulink>.
  Although Debian does not require these to
- be followed, these are still helpful as guidelines and common sense.  (see the local copies of
+ be followed, these are still helpful as guidelines and common sense.
+ (See the local copies of
  <ulink url="&gnu-standard-pdf;">standards.pdf</ulink> and
- <ulink url="&gnu-maintainer-pdf;">maintain.pdf</ulink>).
+ <ulink url="&gnu-maintainer-pdf;">maintain.pdf</ulink>.)
  </para>
  </listitem>
  </itemizedlist>
  <para>
- If this document contradicts with any of the documents mentioned above, they
+ If this document contradicts any of the documents mentioned above, they
  are correct.  Please file a bug report on the
  <systemitem role="package">maint-guide</systemitem> package using
  <command>reportbug</command>.
  </para>
  </section>
- <section id="terminology"><title>Basic terminology</title>
- <para>
- There are two types of packages.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="strong">source package</emphasis>: A source package is a set of
- files which contain code and data which you can compile and process into
- execution programs and formatted documents.  It usually comes as a combination
- of <filename>*.orig.tar.gz</filename>, <filename>*.debian.tar.gz</filename> (or
- <filename>*.diff.gz</filename>), and <filename>*.dsc</filename>.  Some other
- archive and compression methods may be used, too.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="strong">binary package</emphasis>: A binary package contains
- execution programs and formatted documents.  It usually comes as
- <filename>*.deb</filename> for the normal Debian system and as
- <filename>*.udeb</filename> for the Debian Installer.
- </para>
- </listitem>
- </itemizedlist>
- <para>
- Don't mix terms like source of the program and the source package of the
- program!
- </para>
- <para>
- There are several role names used around Debian.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="strong">upstream author</emphasis>: The person who made the
- original program.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="strong">upstream maintainer</emphasis>: The person who
- currently maintains the program.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="strong">maintainer</emphasis>: The person who makes Debian
- package of the program.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="strong">sponsor</emphasis>: The person who helps maintainers to
- upload packages to the official Debian Package Archive after checking their
- contents.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="strong">mentor</emphasis>: The person who helps novice
- maintainers on packaging etc.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="strong">Debian Developer</emphasis> (DD): The person who is a
- member of Debian.  He has full upload right to the official Debian Package
- Archive.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="strong">Debian Maintainer</emphasis> (DM): The person who has
- limited upload right to the official Debian Package Archive.
- </para>
- </listitem>
- </itemizedlist>
- <para>
- There are several version names<footnote><para>See <ulink url="&policy-control;#s-f-Version">Debian Policy  Manual: 5.6.12 Version</ulink>.</para></footnote> used around Debian.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="strong">upstream source version</emphasis>: The upstream source
- version is referred as <literal><replaceable>version</replaceable></literal>.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="strong">Debian revision</emphasis>: The revision by Debian on
- package is referred as <literal><replaceable>revision</replaceable></literal>.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="strong">Debian package version</emphasis>: The Debian package
- version is referred as the following.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <literal><replaceable>version</replaceable></literal> for the native Debian
- binary package and for the Debian source package.
- </para>
- </listitem>
- <listitem>
- <para>
- <literal><replaceable>version</replaceable>-<replaceable>revision</replaceable></literal>
- for the non-native Debian binary package.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- <para>
- Please read the other manuals if you need more details on terminology.
- <footnote><para>See lists in <xref linkend="socialdynamism"/> and <xref linkend="needdocs"/>.</para></footnote>
- </para>
- </section>
  <section id="helpme"><title>Where to ask for help</title>
  <para>
  Before you decide to ask your question in some public place, please read the fine documentation.
-Line 550 
 Before you decide to ask your question i
+Line 494 
 Before you decide to ask your question i
  <itemizedlist>
  <listitem>
  <para>
- files in <filename>/usr/share/doc/dpkg</filename>
+ files in <filename>/usr/share/doc/<replaceable>package</replaceable></filename> for all pertinent packages
- </para>
- </listitem>
- <listitem>
- <para>
- files in <filename>/usr/share/doc/debian</filename>
- <!-- /usr/share/doc/debian is used be doc-debian and debian-faq -->
- </para>
- </listitem>
- <listitem>
- <para>
- files in <filename>/usr/share/doc/autotools-dev</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- files in <filename>/usr/share/doc/<replaceable>package</replaceable></filename> for all pertinent packages.
  </para>
  </listitem>
  <listitem>
-Line 591 
 contents of <ulink url="&debian-devel-ld
+Line 519 
 contents of <ulink url="&debian-devel-ld
  </listitem>
  </itemizedlist>
  <para>
- Please consider to use web search engine effectively by including search string
+ You can use web search engines more effectively by including search strings
  such as <literal>site:lists.debian.org</literal> to limit the domain.
  </para>
  <para>
- Making a small test package is good way to learn details of packaging.
+ Making a small test package is a good way to learn details of packaging.
  Inspecting existing well maintained packages is the best way to learn how other
  people make packages.
  </para>
-Line 630 
 is time for you to dig into the
+Line 558 
 is time for you to dig into the
  <ulink url="&bts;">Debian Bug Tracking System</ulink>
  and read the documentation there, to be able to
  deal with the reports efficiently.  I highly recommend reading the
- <ulink url="&devref-bug-handling;">Debian Developer's Reference, 5.8.  'Handling bugs'</ulink>.
+ <ulink url="&devref-bug-handling;">Debian Developer's Reference, 5.8:
+ "Handling bugs"</ulink>.
  </para>
  <para>
  Even if it all worked well, it's time to start praying.  Why?  Because in just
-Line 648 
 documentation</emphasis> for details).
+Line 577 
 documentation</emphasis> for details).
  </chapter>
  <chapter id="first"><title>First steps</title>
  <para>
- Let's try to make your own package (or, better even, adopt an existing one).
+ Let's start by creating a package of your own (or, even better,
+ adopting an existing one).
+ </para>
+ <para>
+ This involves generating several specifically named files for each step of the
+ Debian package building.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>We obtain an upstream program file usually in a compressed tar format.</para>
+   <itemizedlist>
+   <listitem><literal><replaceable>programname</replaceable>-<replaceable>version</replaceable>.tar.gz</literal></listitem>
+   </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ We create an Debian source package, which reffers to the set of input files for
+ the Debian package building, by adding Debian package modifications to the upstream program.
+ </para>
+   <itemizedlist>
+   <listitem><literal><replaceable>programname</replaceable>_<replaceable>version</replaceable>.orig.tar.gz</literal></listitem>
+   <listitem><literal><replaceable>programname</replaceable>_<replaceable>version</replaceable>-<replaceable>revision</replaceable>.debian.tar.gz</literal></listitem>
+   <listitem><literal><replaceable>programname</replaceable>_<replaceable>version</replaceable>-<replaceable>revision</replaceable>.dsc</literal></listitem>
+   </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ We build Debian binary packages, which are ordinary installable package files in <literal>.deb</literal> format (or <literal>.udeb</literal> format, used by the Debian Installer), from the Debian source package.
+ </para>
+   <itemizedlist>
+   <listitem><literal><replaceable>programname</replaceable>_<replaceable>version</replaceable>-<replaceable>revision</replaceable>.deb</literal></listitem>
+   </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ <para>
+ When there is no complication with the Debian policy,
+ <literal><replaceable>programname</replaceable></literal> is substituted by the
+ <emphasis role="strong">package name</emphasis>,
+ <literal><replaceable>version</replaceable></literal> is substituted by the
+ <emphasis role="strong">upstream version</emphasis>, and
+ <literal><replaceable>revision</replaceable></literal> is substituted by the
+ <emphasis role="strong">Debian revision</emphasis>.
  </para>
  <section id="choose"><title>Choose your program</title>
  <para>
-Line 661 
 using the following.
+Line 631 
 using the following.
  <para>the <command>aptitude</command> command</para>
  </listitem>
  <listitem>
- <para><ulink url="&packages-do;">Debian packages</ulink> web page</para>
+ <para>the <ulink url="&packages-do;">Debian packages</ulink> web page</para>
  </listitem>
  <listitem>
- <para><ulink url="&packages-qa-do;">Debian Package Tracking System</ulink> web page</para>
+ <para>the <ulink url="&packages-qa-do;">Debian Package Tracking System</ulink> web page</para>
  </listitem>
  </itemizedlist>
  <para>
  If the package already exists, well, install it!  :-) If it happens to be
- <emphasis role="strong">orphaned</emphasis> -- if its maintainer is set to
+ <emphasis role="strong">orphaned</emphasis> (that is, if its
- <ulink url="&qa-do;">Debian QA Group</ulink>, you may be able to pick it up if
+ maintainer is set to <ulink url="&qa-do;">Debian QA Group</ulink>),
- it's still available.  You may also adopt a package for which the corresponding
+ you may be able to pick it up if it's still available.  You may also
- maintainer has filed a Request for Adoption
+ adopt a package whose maintainer has filed a Request for Adoption
- (<emphasis role="strong">RFA</emphasis>).
+ (<emphasis role="strong">RFA</emphasis>).<footnote> <para>See
+ <ulink url="&devref-adopt;">Debian Developer's Reference 5.9.5.
+ "Adopting a package"</ulink>.</para> </footnote>
  </para>
  <para>
  There are several package ownership status resources.
-Line 683 
 There are several package ownership stat
+Line 655 
 There are several package ownership stat
  <para> <ulink url="&wnpp-do;">Work-Needing and Prospective Packages</ulink> </para>
  </listitem>
  <listitem>
- <para> <ulink url="&wnpp-bts;">Debian Bug report logs: Bugs in package wnpp in unstable</ulink> </para>
+ <para> <ulink url="&wnpp-bts;">Debian Bug report logs: Bugs in pseudo-package <systemitem role="package">wnpp</systemitem> in <literal>unstable</literal></ulink> </para>
  </listitem>
  <listitem>
  <para> <ulink url="&wnpp-dn;">Debian Packages that Need Lovin'</ulink> </para>
  </listitem>
  <listitem>
- <para> <ulink url="&wnpp-debtags;">Browse WNPP bugs based on debtags</ulink> </para>
+ <para> <ulink url="&wnpp-debtags;">Browse <systemitem role="package">wnpp</systemitem> bugs based on debtags</ulink> </para>
  </listitem>
  </itemizedlist>
  <para>
-Line 698 
 for most kinds of programs, and the numb
+Line 670 
 for most kinds of programs, and the numb
  archive is much larger than that of contributors with upload rights.  Thus,
  contributions to packages already in the archive are far more appreciated (and
  more likely to receive sponsorship) by other developers <footnote><para> Having
- said that, there will of course always be new programs that are worthwhile
+ said that, there will of course always be new programs that are worth
- packaging.  </para> </footnote>.  You can do that in various ways.
+ packaging.  </para> </footnote>.  You can contribute in various ways.
  </para>
  <itemizedlist>
  <listitem>
-Line 729 
 If you are able to adopt the package, ge
+Line 701 
 If you are able to adopt the package, ge
  examine them.  This document unfortunately doesn't include comprehensive
  information about adopting packages.  Thankfully you shouldn't have a hard time
  figuring out how the package works since someone has already done the initial
- set up for you.  Keep reading, though, a lot of the advice below will still be
+ setup for you.  Keep reading, though; a lot of the advice below will still be
  applicable for your case.
  </para>
  <para>
-Line 739 
 as follows:
+Line 711 
 as follows:
  <itemizedlist>
  <listitem>
  <para>
- First, you must know that program works, and have tried it for some time to
+ First, you must know that the program works, and have tried it for some time to
  confirm its usefulness.
  </para>
  </listitem>
  <listitem>
  <para>
- You must check if no one else is working on the package already at the
+ You must check that no one else is already working on the package on the
  <ulink url="&wnpp-do;">Work-Needing and Prospective Packages</ulink> site.
  If no one else is working on it, file an ITP (Intent
  To Package) bug report to the <systemitem role="package">wnpp</systemitem>
  pseudo-package using <command>reportbug</command>.  If someone's already on it,
  contact them if you feel you need to.  If not - find another interesting
- program that nobody maintains.
+ program that nobody is maintaining.
  </para>
  </listitem>
  <listitem>
  <para>
- That program <emphasis role="strong">must have a license</emphasis>.
+ The software <emphasis role="strong">must have a license</emphasis>.
  </para>
  <itemizedlist>
  <listitem>
  <para>
- For the <literal>main</literal> section, it <emphasis role="strong">must be
+ For the <literal>main</literal> section, Debian Policy requires it
- compliant to all the Debian Free Software Guidelines</emphasis> (<ulink url="&dfsg;">DFSG</ulink>)
+ <emphasis role="strong">to be fully compliant with the Debian Free Software
- and <emphasis role="strong">that program must not require a package outside of
+ Guidelines</emphasis> (<ulink url="&dfsg;">DFSG</ulink>)
- <literal>main</literal></emphasis> for compilation or execution as required by
+ and <emphasis role="strong">not to require a package outside of
- the Debian Policy.  This is desired case.
+ <literal>main</literal></emphasis> for compilation or execution.  This
+ is the desired case.
  </para>
  </listitem>
  <listitem>
  <para>
- For the <literal>contrib</literal> section, it must be compliant to all the
+ For the <literal>contrib</literal> section, it must comply with the
  DFSG but it may require a package outside of <literal>main</literal> for
  compilation or execution.
  </para>
  </listitem>
  <listitem>
  <para>
- For the <literal>non-free</literal> section, it may not be compliant to some of
+ For the <literal>non-free</literal> section, it may be non-compliant
- the DFSG but it <emphasis role="strong">must be distributable</emphasis>.
+ with the DFSG but it <emphasis role="strong">must be distributable</emphasis>.
  </para>
  </listitem>
  </itemizedlist>
-Line 789 
 and ask for advice.
+Line 762 
 and ask for advice.
  </listitem>
  <listitem>
  <para>
- That program certainly should <emphasis role="strong">not</emphasis> run setuid
+ The program certainly should <emphasis role="strong">not</emphasis> run setuid
- root, or even better - it shouldn't need to be setuid or setgid to anything.
+ root, or even better, it shouldn't need to be setuid or setgid to anything.
  </para>
  </listitem>
  <listitem>
  <para>
- That program should not be a daemon, or something that goes in
+ The program should not be a daemon, or go in an
- <filename>*/sbin</filename> directories, or open a port as root.
+ <filename>*/sbin</filename> directory, or open a port as root.
  </para>
  </listitem>
  <listitem>
  <para>
- That program should result in binary executable form, libraries are harder to
+ The program should be in binary executable form; libraries are harder to handle.
- handle.
  </para>
  </listitem>
  <listitem>
  <para>
- That program should be well documented and its code needs to be understandable
+ The program should be well documented and its code needs to be understandable
  (i.e.  not obfuscated).
  </para>
  </listitem>
  <listitem>
  <para>
- You should contact program's author(s) to check if they agree with packaging it
+ You should contact the program's author(s) to check if they agree with packaging it
- and amicable to Debian.  It is important to be able to consult with author(s)
+ and are amicable to Debian.  It is important to be able to consult with the author(s)
- about the program in case of any program specific problems, so don't try to
+ in case of any problems with the program, so don't try to package
- package unmaintained pieces of software.
+ unmaintained software.
  </para>
  </listitem>
  </itemizedlist>
  <para>
- Of course, these things are just safety measures, and intended to save you from
+ Of course, these are just safety measures, and intended to save you from
- raging users if you do something wrong in some setuid daemon...  When you gain
+ enraging users if you do something wrong in some setuid daemon...  When you gain
- some more experience in packaging, you'll be able to package such packages.
+ more experience in packaging, you'll be able to package such software.
  </para>
  </section>
  <section id="getit"><title>Get the program, and try it out</title>
  <para>
- So the first thing to do is to find and download the original source code.  I
+ So the first thing to do is to find and download the original source code.
- presume that you already have the source file that you picked up at the
+ Presumably you already have the source file that you picked up at the
  author's homepage.  Sources for free Unix programs usually come in
- <command>tar</command>+<command>gzip</command> format with extension
+ <command>tar</command>+<command>gzip</command> format with the extension
  <filename>.tar.gz</filename>, or
- <command>tar</command>+<command>bzip2</command> format with extension
+ <command>tar</command>+<command>bzip2</command> format with the extension
- <filename>.tar.bz2</filename>.  These usually contain the subdirectory called
+ <filename>.tar.bz2</filename>.  These usually contain a directory called
  <filename><replaceable>programname</replaceable>-<replaceable>version</replaceable></filename>
- in them and all the sources under it.
+ with all the sources inside.
  </para>
  <para>
- If the latest version of such sources are available through VCS such as Git,
+ If the latest version of the source is available through a VCS such as Git,
- Subversion, or CVS repository, you need to get it with <literal>git
+ Subversion, or CVS, you need to get it with <literal>git
  clone</literal>, <literal>svn co</literal>, or <literal>cvs co</literal> and
- repack it into <command>tar</command>+<command>gzip</command> format by
+ repack it into <command>tar</command>+<command>gzip</command> format yourself
- yourself using the <literal>--exclude-vcs</literal> option.
+ by using the <literal>--exclude-vcs</literal> option.
  </para>
  <para>
  If your program's source comes as some other sort of archive (for instance, the
  filename ends in <filename>.Z</filename> or
  <filename>.zip</filename><footnote><para> You can identify the archive format
  using the <command>file</command> command when the file extension is not
- enough.  </para> </footnote>), unpack it with appropriate tools and repack it,
+ enough.  </para> </footnote>), you should also unpack it with the
- too.
+ appropriate tools and repack it.
  </para>
  <para>
- As an example, I'll use a program called <command>gentoo</command>, an X GTK+
+ As an example, I'll use a program called <command>gentoo</command>, a GTK+
  file manager.
- <footnote><para> This program is already packaged. Its
+ <footnote><para> This program is already packaged. The
  <ulink url="&gentoo-package;">current version</ulink> uses Autotools as its
- build structure and is substantially different from the following examples
+ build structure and is substantially different from the following examples,
- based on the version 0.9.12.</para>
+ which were based on version 0.9.12.</para>
  </footnote>
  </para>
  <para>
-Line 867 
 Create a subdirectory under your home di
+Line 839 
 Create a subdirectory under your home di
  <filename>debian</filename> or <filename>deb</filename> or anything you find
  appropriate (e.g.  just <filename>~/gentoo</filename> would do fine in this
  case).  Place the downloaded archive in it, and extract it (with <literal>tar
- xzf gentoo-0.9.12.tar.gz</literal>).  Make sure there are no errors, even some
+ xzf gentoo-0.9.12.tar.gz</literal>).  Make sure there are no warning
- <emphasis>irrelevant</emphasis> ones, because there will most probably be
+ messages, even <emphasis>irrelevant</emphasis> ones, because other
- problems unpacking on other people's systems, whose unpacking tools may or may
+ people's unpacking tools may or may not ignore these anomalies, so they
- not ignore those anomalies.  On your console screen, you should see the
+ may have problems unpacking them.  Your shell commandline may look
- following.
+ something like this:
  </para>
  <screen>
  $ mkdir ~/gentoo ; cd ~/gentoo
-Line 886 
 Now you have another subdirectory, calle
+Line 858 
 Now you have another subdirectory, calle
  Change to that directory and <emphasis>thoroughly</emphasis> read the provided
  documentation.  Usually there are files named <filename>README*</filename>,
  <filename>INSTALL*</filename>, <filename>*.lsm</filename> or
- <filename>*.html</filename>.  You must find instructions on how to correctly
+ <filename>*.html</filename>.  You must find instructions on how to
  compile and install the program (most probably they'll assume you want to
- install to <filename>/usr/local/bin</filename> directory; you won't be doing
+ install to the <filename>/usr/local/bin</filename> directory; you won't be doing
- that, but more on that later in <xref linkend="destdir"/> ).
+ that, but more on that later in <xref linkend="destdir"/>).
  </para>
  <para>
- Simple programs come with a <filename>Makefile</filename> file in them and can
+ Simple programs come with a <filename>Makefile</filename> and can
- be compiled simply with <literal>make</literal>.<footnote><para>
+ be compiled just by invoking <literal>make</literal>.<footnote><para>
  Many modern programs come with a script <filename>configure</filename> which
- creates a <filename>Makefile</filename> file customized for your system upon
+ when executed creates a <filename>Makefile</filename> customized for
- its execution.</para></footnote> Some of them support
+ your system.</para></footnote> Some of them support
- <literal>make check</literal>, which runs included self-checks.  Installation
+ <literal>make check</literal>, which runs included self-tests.  Installation
  to the destination directories is usually done with <literal>make
  install</literal>.
  </para>
-Line 914 
 all the installed files.
+Line 886 
 all the installed files.
  </section>
  <section id="portable"><title>Free portable programs</title>
  <para>
- A lot of Free programs are written in the <ulink url="&c-program;">C</ulink> and
+ A lot of free software is written in the <ulink url="&c-program;">C</ulink> and
  <ulink url="&cxx;">C++</ulink> languages.  Many of
  these use Autotools or CMake to make them portable across different platforms.
- These tools are used to generate <filename>Makefile</filename> and other
+ These tools are used to generate the <filename>Makefile</filename> and other
- required source files.  Then, such programs are built with usual <literal>make;
+ required source files.  Then, such programs are built using the usual
- make install</literal>.
+ <literal>make; make install</literal>.
  </para>
  <para>
- <ulink url="&gnu-build-system;">Autotools</ulink>
+ <ulink url="&gnu-build-system;">Autotools</ulink> is the GNU build
- are the GNU build system comprising <ulink url="&autoconf;">Autoconf</ulink>, <ulink url="&automake;">Automake</ulink>, <ulink url="&libtool;">Libtool</ulink>, and <ulink url="&gettext;">gettext</ulink>.  You can notice
+ system comprising <ulink url="&autoconf;">Autoconf</ulink>,
+ <ulink url="&automake;">Automake</ulink>,
+ <ulink url="&libtool;">Libtool</ulink>, and
+ <ulink url="&gettext;">gettext</ulink>.  You can recognize
  such sources by the <filename>configure.ac</filename>,
  <filename>Makefile.am</filename>, and <filename>Makefile.in</filename> files.
- <footnote><para> See <ulink url="&autotools-tutorial;">Autotools Tutorial</ulink>
+ <footnote><para> See the <ulink url="&autotools-tutorial;">Autotools Tutorial</ulink>
  and <ulink url="&autotools-readme;"/>.  </para> </footnote>
  </para>
  <para>
- The first step of Autotools work flow is usually that the upstream runs
+ The first step of the Autotools workflow is usually that upstream runs
- <literal>autoreconf -i -f</literal> in the source and distributes this source
+ <literal>autoreconf -i -f</literal> in the source directory and
- with generated files.
+ distributes the generated files along with the source.
  </para>
  <screen>
  configure.ac-----+-&gt; autoreconf -+-&gt; configure
-Line 951 
 files requires some knowledge of <comman
+Line 926 
 files requires some knowledge of <comman
  <literal>info automake</literal>.
  </para>
  <para>
- The second step of Autotools work flow is usually that the user obtains this
+ The second step of the Autotools workflow is usually that the user obtains this
  distributed source and runs <literal>./configure &amp;&amp; make</literal> in
- the source to compile program into a
+ the source directory to compile the program into a
  <command><replaceable>binary</replaceable></command>.
  </para>
  <screen>
-Line 965 
 config.h.in -----+                +-&gt;
+Line 940 
 config.h.in -----+                +-&gt;
             config.guess --+
  </screen>
  <para>
- You can change many things in the <filename>Makefile</filename> file such as
+ You can change many things in the <filename>Makefile</filename>; for
- the default file install location using the command option, e.g.
+ instance you can change the default location for file installation
- <command>./configure --prefix=/usr</command>.
+ using the option <command>./configure --prefix=/usr</command>.
  </para>
  <para>
  Although it is not required, updating the <filename>configure</filename> and
- other files with <literal>autoreconf -i -f</literal> as the user may improve
+ other files with <literal>autoreconf -i -f</literal> may improve
  the compatibility of the source.
  <footnote><para>You can automate this by using
- <systemitem role="package">dh_autoreconf</systemitem> package.
+ <systemitem role="package">dh-autoreconf</systemitem> package.
  See <xref linkend="customrules"/>.</para></footnote>
  </para>
  <para>
  <ulink url="&cmake;">CMake</ulink> is an alternative
- build system.  You can notice such sources by the
+ build system.  You can recognize such sources by the
  <filename>CMakeLists.txt</filename> file.
  </para>
  </section>
-Line 996 
 to
+Line 971 
 to
  </para>
  <para>
  If the program name consists of more than one word, contract them to one word,
- or make an abbreviation.  For example, program John's little editor for X
+ or make an abbreviation.  For example, a package of the program "John's little
- package would be named <systemitem role="package">johnledx</systemitem>, or
+ editor for X" might be named <systemitem role="package">johnledx</systemitem>, or
  <systemitem role="package">jle4x</systemitem>, or whatever you decide, as long
- as it's under some reasonable limit, e.g.  20 characters.
+ as it's under some reasonable length limit, e.g. 20 characters.
  </para>
  <para>
  Also check for the exact version of the program (to be included in the package
- version).  If that piece of software is not numbered with versions like
+ version).  If this piece of software is not numbered with versions like
  <literal>X.Y.Z</literal>, but with some kind of date, feel free to use that
  date as the version number, as long as newer version numbers will look larger.
- While it is best to use the same version number as what upstream uses, if it is
+ While it is best to use the same version numbering as upstream, if it is
  in the format of <literal>09Oct23</literal> you may need to convert it to
  <literal>YYYYMMDD</literal> format, which would be <literal>20091023</literal>,
- to ensure proper order for upgrade with the <command>dpkg</command>
+ to ensure that <command>dpkg</command> sees later versions as
- program.<footnote><para> Version string can be compared by <literal>dpkg
+ upgrades.<footnote><para> Version strings can be compared with <literal>dpkg
  --compare-versions <replaceable>ver1</replaceable>
  <replaceable>op</replaceable> <replaceable>ver2</replaceable></literal>.  See
  <citerefentry> <refentrytitle>dpkg</refentrytitle> <manvolnum>1</manvolnum>
- </citerefentry> manpage.  </para> </footnote>
+ </citerefentry>.  </para> </footnote>
  </para>
  <para>
  Some programs won't be numbered at all, in which case you should contact the
-Line 1023 
 upstream maintainer to see if they've go
+Line 998 
 upstream maintainer to see if they've go
  </section>
  <section id="dh-make"><title>Initial Debian package</title>
  <para>
- Let's set up the shell environment variable <literal>$DEBEMAIL</literal> and
+ Set up the shell environment variables <literal>$DEBEMAIL</literal> and
- <literal>$DEBFULLNAME</literal> so many Debian maintenance tools recognize your
+ <literal>$DEBFULLNAME</literal> so that various Debian maintenance
- name and email address to use for packages as follows.<footnote><para> The
+ tools recognize your email address and name to use for packages.<footnote><para> The
  following text assumes you are using Bash as your login shell.  If you use
- other login shells such as Z shell, use their pertinent configuration files
+ some other login shell such as Z shell, use their corresponding
- instead of <filename>~/.bashrc</filename>.  </para> </footnote>.
+ configuration files instead of <filename>~/.bashrc</filename>. </para> </footnote>.
  </para>
  <screen>
  $ cat &gt;&gt;~/.bashrc &lt;&lt;EOF
-Line 1038 
 export DEBEMAIL DEBFULLNAME
+Line 1013 
 export DEBEMAIL DEBFULLNAME
  EOF
  </screen>
  <para>
- Let's make an initial Debian package by issuing the <command>dh_make</command>
+ You can create an initial Debian package by issuing the
- command as follows.
+ <command>dh_make</command> command as follows.
  </para>
  <screen>
  $ . ~/.bashrc
-Line 1050 
 $ dh_make -f ../gentoo-0.9.12.tar.gz
+Line 1025 
 $ dh_make -f ../gentoo-0.9.12.tar.gz
  Of course, replace the filename with the name of your original source archive.
  <footnote><para> If the upstream source provides the
  <filename>debian</filename> directory and its contents, run the
- <command>dh_make</command> command with the <literal>--addmissing</literal>
+ <command>dh_make</command> command with the extra option
- option, instead.  The new source <literal>3.0 (quilt)</literal> format is quite
+ <literal>--addmissing</literal>.  The new source <literal>3.0 (quilt)</literal> format is
- robust not to break even for these packages.  You may need to update contents
+ robust enough not to break even for these packages.  You may need to update the contents
  provided by the upstream for your Debian package.  </para> </footnote> See
  <citerefentry> <refentrytitle>dh_make</refentrytitle> <manvolnum>1</manvolnum>
  </citerefentry> for details.
  </para>
  <para>
- Some information will come up.  It will ask you what sort of package you want
+ You should see some output asking you what sort of package you want
  to create.  Gentoo is a single binary package - it creates only one binary, and
- thus one <filename>.deb</filename> file - so we will select the first option,
+ thus one <filename>.deb</filename> file - so we will select the first option
- with the <literal>s</literal> key, check the information on the screen and
+ (with the <literal>s</literal> key), check the information on the screen, and
  confirm by pressing <literal><replaceable>ENTER</replaceable></literal>.
- <footnote><para> There are few choices here: <literal>s</literal> for Single
+ <footnote><para> There are several choices here: <literal>s</literal> for Single
- binary, <literal>i</literal> for Arch-Independent, <literal>m</literal> for
+ binary, <literal>i</literal> for arch-Independent, <literal>m</literal> for
  Multiple binary, <literal>l</literal> for Library, <literal>k</literal> for
- Kernel module, <literal>n</literal> for Kernel patch and <literal>b</literal>
+ Kernel module, <literal>n</literal> for kernel patch, and <literal>b</literal>
  for <systemitem role="package">cdbs</systemitem>.  This document focuses on the
- use of the <systemitem role="package">debhelper</systemitem> package with the
+ use of the <command>dh</command> command (from the package
- <command>dh</command> command.  This document focuses on the use of the new
+ <systemitem role="package">debhelper</systemitem>) to create a single-binary package,
- <command>dh</command> command for Single binary and touches on it for
+ but also touches on how to use it for arch-independent or
- Arch-Independent and Multiple binary.  The <systemitem role="package">cdbs</systemitem> package offers alternative package script
+ multiple-binary packages.  The package
- infrastructure to the <command>dh</command> command and outside of the scope of
+ <systemitem role="package">cdbs</systemitem> offers an alternative packaging script
+ infrastructure to the <command>dh</command> command and is outside the scope of
  this document.  </para> </footnote>
  </para>
  <para>
- After this execution of <command>dh_make</command>, a copy of the upstream
+ This execution of <command>dh_make</command> creates a copy of the upstream
- tarball is created as <filename>gentoo_0.9.12.orig.tar.gz</filename> in the
+ tarball as <filename>gentoo_0.9.12.orig.tar.gz</filename> in the
  parent directory to accommodate the creation of the non-native Debian source
- package with the <filename>debian.tar.gz</filename> later.
+ package with the name <filename>debian.tar.gz</filename> later.
  </para>
  <screen>
  $ cd ~/gentoo ; ls -F
-Line 1088 
 gentoo-0.9.12.tar.gz
+Line 1064 
 gentoo-0.9.12.tar.gz
  gentoo_0.9.12.orig.tar.gz
  </screen>
  <para>
- Please note 2 key features in this
+ Please note two key features of this filename
- <filename>gentoo_0.9.12.orig.tar.gz</filename> file name:
+ <filename>gentoo_0.9.12.orig.tar.gz</filename>:
  </para>
  <itemizedlist>
  <listitem>
  <para>
- Package name and version are separated by the <literal>_</literal>
+ Package name and version are separated by the character <literal>_</literal>
  (underscore).
  </para>
  </listitem>
  <listitem>
  <para>
- There is the <filename>.orig</filename> before the
+ The string <filename>.orig</filename> is inserted before the
  <filename>.tar.gz</filename>.
  </para>
  </listitem>
  </itemizedlist>
  <para>
  You should also notice that many template files are created in the source under
- the <filename>debian</filename> directory.  These will be explained in <xref linkend="dreq"/> and <xref linkend="dother"/> .  You should also understand
+ the <filename>debian</filename> directory.  These will be explained in
- that the packaging is not automatic process.  You need to modify the upstream
+ <xref linkend="dreq"/> and <xref linkend="dother"/>.  You should also understand
- source for Debian as <xref linkend="modify"/> .  After all these, you need to
+ that packaging cannot be a fully automated process.  You will need to modify the upstream
- build Debian packages under the proper method as <xref linkend="build"/> ,
+ source for Debian (see <xref linkend="modify"/>).  After this, you need to
- check them as <xref linkend="checkit"/> , and upload them as <xref linkend="upload"/> .  I will explain all these steps.
+ use the proper methods for building Debian packages (<xref linkend="build"/>),
+ testing them (<xref linkend="checkit"/>), and uploading them (<xref linkend="upload"/>).
+ All the steps will be explained.
  </para>
  <para>
  Once again, as a new maintainer you are discouraged from creating complicated
- packages, e.g.,
+ packages, e.g.:
  </para>
  <itemizedlist>
  <listitem>
  <para>
- multiple binary packages,
+ multiple binary packages;
  </para>
  </listitem>
  <listitem>
  <para>
- library packages,
+ library packages;
  </para>
  </listitem>
  <listitem>
  <para>
- kernel module packages,
+ kernel module packages;
  </para>
  </listitem>
  <listitem>
  <para>
- kernel patch packages,
+ kernel patch packages;
  </para>
  </listitem>
  <listitem>
  <para>
- the source file format being neither in <filename>tar.gz</filename> nor
+ packages with the source in a format other than <filename>tar.gz</filename> or
- <filename>tar.bz2</filename>, or
+ <filename>tar.bz2</filename>; or
  </para>
  </listitem>
  <listitem>
  <para>
- the source tarball containing undistributable contents.
+ packages where the source tarball contains undistributable contents.
  </para>
  </listitem>
  </itemizedlist>
  <para>
- It's not too hard, but it does require a bit more knowledge, so we won't
+ Doing so is not too hard, but it requires a bit more knowledge, so we won't
  describe all of it here.
  </para>
  <para>
-Line 1161 
 recover them by running <command>dh_make
+Line 1139 
 recover them by running <command>dh_make
  </para>
  <para>
  Updating an existing package may get complicated since it may be using older
- techniques.  Please stick with fresh packaging cases for now to learn basics.
+ techniques.  While learning the basics, please stick to creating a fresh
- I will come back to explain it later in <xref linkend="update"/> .
+ package; further explanations are given in <xref linkend="update"/>.
  </para>
  </section>
  </chapter>
-Line 1180 
 default is desirable, let's create an al
+Line 1158 
 default is desirable, let's create an al
  Debian packaging by adding the following line to <filename>~/.bashrc</filename>.
  </para>
  <screen>
- alias dquilt=quilt --quiltrc=~/.quiltrc-dpkg
+ alias dquilt="quilt --quiltrc=~/.quiltrc-dpkg"
  </screen>
  <para>
  Then let's create <filename>~/.quiltrc-dpkg</filename> as follows.
-Line 1531 
 that we should edit in order to customiz
+Line 1509 
 that we should edit in order to customiz
  most important of them are <filename>control</filename>,
  <filename>changelog</filename>, <filename>copyright</filename> and
  <filename>rules</filename>, which are required for all packages.
+ <footnote><para>
+ In this chapter, files in the <filename>debian</filename> directory are
+ referred without preceding <filename>debian/</filename> for simplicity whenever
+ they are obvious.
+ </para></footnote>
  </para>
  <section id="control"><title><filename>control</filename> file</title>
  <para>
-Line 1586 
 daemons, <literal>x11</literal> for X11
+Line 1569 
 daemons, <literal>x11</literal> for X11
  and many more.
  <footnote> <para>See
  <ulink url="&policy-subsections;">Debian Policy Manual, 2.4 'Sections'</ulink> and
- <ulink url="&sections-unstable;">List of sections in 'sid'</ulink>.</para>
+ <ulink url="&sections-unstable;">List of sections in <literal>sid</literal></ulink>.</para>
  </footnote>
  </para>
  <para>
-Line 1660 
 satisfy the Debian Policy requirement fo
+Line 1643 
 satisfy the Debian Policy requirement fo
  For source packages which have some binary packages with <literal>Architecture:
  any</literal>, they are rebuild by the autobuilder.  Since this autobuilder
  procedure runs <literal>debian/rules build</literal> in it while installing
- only packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="autobuilder"/> ), the <literal>Build-Depends</literal> field needs to
+ only packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="autobuilder"/>), the <literal>Build-Depends</literal> field needs to
  list practically all the required packages and the
  <literal>Build-Depends-indep</literal> is rarely used.
  </para>
-Line 1896 
 substituting <literal>${shlibs:Depends}<
+Line 1879 
 substituting <literal>${shlibs:Depends}<
  </para>
  <para>
  <citerefentry> <refentrytitle>dh_perl</refentrytitle> <manvolnum>1</manvolnum>
- </citerefentry> calculates perl dependencies.  It generates a list of a
+ </citerefentry> calculates Perl dependencies.  It generates a list of a
- dependency on perl or perlapi for each binary package.  Such list is used for
+ dependency on <literal>perl</literal> or <literal>perlapi</literal> for each binary package.  Such list is used for
  substituting <literal>${perl:Depends}</literal>.
  </para>
  <para>
-Line 1990 
 This file contains the information about
+Line 1973 
 This file contains the information about
  and license information.
  <ulink url="&policy-copyright;">Debian Policy Manual, 12.5 'Copyright information'</ulink>
  dictates its content and
- <ulink url="&dep5;">DEP-5: Machine-parseable debian/copyright</ulink>
+ <ulink url="&dep5;">DEP-5: Machine-parseable <filename>debian/copyright</filename></ulink>
  provides guidelines for its format.
  </para>
  <para>
-Line 2122 
 You will end up with something like this
+Line 2105 
 You will end up with something like this
  </para>
  <para>
  You can read more about updating the <filename>changelog</filename> file later
- in <xref linkend="update"/> .
+ in <xref linkend="update"/>.
  </para>
  </section>
  <section id="rules"><title><filename>rules</filename> file</title>
-Line 2171 
 binary package under the <filename>debia
+Line 2154 
 binary package under the <filename>debia
  <literal>binary</literal> target: to create all binary packages (effectively
  combination of <literal>binary-arch</literal> and
  <literal>binary-indep</literal> targets).  (required)<footnote><para> This
- target is used by <literal>dpkg-buildpackage</literal> as in <xref linkend="completebuild"/> .  </para> </footnote>
+ target is used by <literal>dpkg-buildpackage</literal> as in <xref linkend="completebuild"/>.  </para> </footnote>
  </para>
  </listitem>
  <listitem>
-Line 2179 
 target is used by <literal>dpkg-buildpac
+Line 2162 
 target is used by <literal>dpkg-buildpac
  <literal>binary-arch</literal> target: to create arch-dependent
  (<literal>Architecture: any</literal>) binary packages in the parent directory.
  (required)<footnote><para> This target is used by <literal>dpkg-buildpackage
- -B</literal> as in <xref linkend="autobuilder"/> .  </para> </footnote>
+ -B</literal> as in <xref linkend="autobuilder"/>.  </para> </footnote>
  </para>
  </listitem>
  <listitem>
-Line 2244 
 It tells the operating system that this
+Line 2227 
 It tells the operating system that this
  <filename>/usr/bin/make</filename>.
  </para>
  <para>
- Line 10 can be uncommented to set <literal>DH_VERBOSE</literal> variable to 1.
+ Line 11 can be uncommented to set <literal>DH_VERBOSE</literal> variable to 1.
  Then, the <command>dh</command> command will output which
  <command>dh_*</command> commands are executed by the <command>dh</command>
  command.  You can also add <literal>export DH_OPTIONS=-v</literal> line here.
-Line 2266 
 complicated <filename>rules</filename> f
+Line 2249 
 complicated <filename>rules</filename> f
  scripts listed for each required explicit targets and frozen them to the state
  when it was initially packaged.  This new <command>dh</command> command is
  simpler and frees us from this constrain.  You still have full power to
- customize this with <literal>override_dh_*</literal> targets.  See <xref linkend="customrules"/> .  It is based only on the <systemitem role="package">debhelper</systemitem> package and does not obfuscate the
+ customize this with <literal>override_dh_*</literal> targets.  See <xref linkend="customrules"/>.  It is based only on the <systemitem role="package">debhelper</systemitem> package and does not obfuscate the
  package building process like the <systemitem role="package">cdbs</systemitem>
  package.  </para> </footnote> The <command>dh</command> command is a wrapper
  script which runs appropriate sequences of <command>dh_*</command> programs
-Line 2680 
 This installs <command>bash</command> co
+Line 2663 
 This installs <command>bash</command> co
  </listitem>
  </itemizedlist>
  <para>
- For sources using Autotools, use combination of above as <literal>dh --with
- autotools-dev --with autoreconf $@</literal> to be most current with the GNU
- Build System.
- </para>
- <para>
  Many <command>dh_*</command> commands invoked by the new <command>dh</command>
  command can be customized by the corresponding configuration files in the
  <filename>debian</filename> directory.  See <xref linkend="dother"/> and the
-Line 2809 
 filenames suffixed by <literal>.ex</lite
+Line 2787 
 filenames suffixed by <literal>.ex</lite
  prefixed by the binary package name such as
  <literal><replaceable>package</replaceable></literal>.  Take a look at all of
  them.
+ <footnote><para>
+ In this chapter, files in the <filename>debian</filename> directory are
+ referred without preceding <filename>debian/</filename> for simplicity whenever
+ they are obvious.
+ </para></footnote>
  </para>
  <para>
  The <command>dh_make</command> command may not create some template
-Line 2843 
 remove template files which you do not n
+Line 2826 
 remove template files which you do not n
  </listitem>
  <listitem>
  <para>
- modify the <filename>control</filename> file (see <xref linkend="control"/> ),
+ modify the <filename>control</filename> file (see <xref linkend="control"/>),
  if necessary.
  </para>
  </listitem>
  <listitem>
  <para>
- modify the <filename>rules</filename> file (see <xref linkend="rules"/> ), if
+ modify the <filename>rules</filename> file (see <xref linkend="rules"/>), if
  necessary.
  </para>
  </listitem>
-Line 2940 
 the <filename>/etc</filename> directory.
+Line 2923 
 the <filename>/etc</filename> directory.
  </listitem>
  </itemizedlist>
  <para>
- For more information on the <emphasis>maintainer scripts</emphasis>, see <xref linkend="maintscripts"/> .
+ For more information on the <emphasis>maintainer scripts</emphasis>, see <xref linkend="maintscripts"/>.
  </para>
  </section>
  <section id="crond"><title><filename><replaceable>package</replaceable>.cron.*</filename> files</title>
-Line 3009 
 means there is a problem with the <filen
+Line 2992 
 means there is a problem with the <filen
  </para>
  <para>
  Files listed in the <filename>install</filename> file doesn't need the
- directories created first.  See <xref linkend="install"/> .
+ directories created first.  See <xref linkend="install"/>.
  </para>
  <para>
  It is best to try to run the installation first and only use this if you
-Line 3052 
 For information on the file format, see
+Line 3035 
 For information on the file format, see
  manual, in <ulink url="&doc-base;">Debian doc-base Manual</ulink>.
  </para>
  <para>
- For more details on installing additional documentation, look in <xref linkend="destdir"/> .
+ For more details on installing additional documentation, look in <xref linkend="destdir"/>.
  </para>
  </section>
  <section id="docs"><title><filename>docs</filename> file</title>
-Line 3110 
 obviously disregarded my initial recomme
+Line 3093 
 obviously disregarded my initial recomme
  <para>
  The <filename><replaceable>package</replaceable>.init</filename> file is
  installed as the
- <filename>/etc/init.d/<replaceable>package</replaceable></filename> script.
+ <filename>/etc/init.d/<replaceable>package</replaceable></filename> script
+ for the <emphasis>init script</emphasis> which starts and stops a daemon.
  Its fairly generic skeleton template is provided by the
  <command>dh_make</command> command as <filename>init.d.ex</filename>.  You'll
  likely have to rename and edit it, a lot, while making sure to provide
-Line 3123 
 gets installed into the temporary direct
+Line 3107 
 gets installed into the temporary direct
  The <filename><replaceable>package</replaceable>.default</filename> file will
  be installed into
  <filename>/etc/default/<replaceable>package</replaceable></filename>.  This
- file sets defaults that are sourced by the init script.  Most times this
+ file sets defaults that are sourced by the <emphasis>init script</emphasis>.  Most times this
- default file is used to disable running a daemon, set some default flags or
+ <filename><replaceable>package</replaceable>.default</filename> file is used to disable running a daemon, set some default flags or
- timeouts.  If your init script has certain <emphasis>settable</emphasis>
+ timeouts.  If your <emphasis>init script</emphasis> has certain <emphasis>settable</emphasis>
- features you want to install these into the default file, not the init script.
+ features you want to install these into the <filename><replaceable>package</replaceable>.default</filename> file, not the <emphasis>init script</emphasis>.
  </para>
  <para>
- If your upstream program has an init file you can either use it or not.  If you
+ If your upstream program provides a file for the <emphasis>init script</emphasis>, you can either use it or not.  If you
- don't use their init.d script then create a new one in
+ don't use their <emphasis>init script</emphasis> then create a new one in
- <filename>debian/<replaceable>package</replaceable>.init</filename>.  However
+ <filename><replaceable>package</replaceable>.init</filename>.  However
- if the upstream init script looks fine and installs in the right place you
+ if the upstream <emphasis>init script</emphasis> looks fine and installs in the right place you
  still need to setup the <filename>rc*</filename> symlinks.  To do this you will
  need to override <command>dh_installinit</command> in the
  <filename>rules</filename> file with the following lines:
-Line 3251 
 list of manual page sections:
+Line 3235 
 list of manual page sections:
      <row> <entry>1</entry> <entry>User command</entry> <entry>Executable commands or scripts</entry> </row>
      <row> <entry>2</entry> <entry>System calls</entry> <entry>Functions provided by the kernel</entry> </row>
      <row> <entry>3</entry> <entry>Library calls</entry> <entry>Functions within system libraries</entry> </row>
-     <row> <entry>4</entry> <entry>Special files</entry> <entry>Usually found in /dev</entry> </row>
+     <row> <entry>4</entry> <entry>Special files</entry> <entry>Usually found in <filename>/dev</filename></entry> </row>
      <row> <entry>5</entry> <entry>File formats</entry> <entry>E.g. <filename>/etc/passwd</filename>'s format</entry> </row>
      <row> <entry>6</entry> <entry>Games</entry> <entry>Games or other frivolous programs</entry> </row>
-     <row> <entry>7</entry> <entry>Macro packages</entry> <entry>Such as man macros</entry> </row>
+     <row> <entry>7</entry> <entry>Macro packages</entry> <entry>Such as <command>man</command> macros</entry> </row>
      <row> <entry>8</entry> <entry>System administration</entry> <entry>Programs typically only run by root</entry> </row>
      <row> <entry>9</entry> <entry>Kernel routines</entry> <entry>Non-standard calls and internals</entry> </row>
    </tbody>
-Line 3619 
 creating the source package.
+Line 3603 
 creating the source package.
  You can store such <command>dpkg-source</command> option argument in the
  <filename>source/options</filename> file of the source package as the generic
  solution to address this problem of the autogenerated files.  The following
- will skip creating patch files for <filename>config.sub</filename>
+ will skip creating patch files for <filename>config.sub</filename>,
  <filename>config.guess</filename> and <filename>Makefile</filename>.
  </para>
  <screen>
-Line 3664 
 documentation of your changes are very i
+Line 3648 
 documentation of your changes are very i
  by your sponsor.  </para> </footnote>
  </para>
  <para>
- For <xref linkend="modify"/> , we created 3 patches in
+ For <xref linkend="modify"/>, we created 3 patches in
  <filename>debian/patches</filename>.
  </para>
  <para>
  Since Debian patches are located in <filename>debian/patches</filename>, please
  make sure to setup the <command>dquilt</command> command properly as described
- in <xref linkend="quiltrc"/> .
+ in <xref linkend="quiltrc"/>.
  </para>
  <para>
  When someone (including yourself) provides you with a patch
-Line 3711 
 the <systemitem role="package">build-ess
+Line 3695 
 the <systemitem role="package">build-ess
  </listitem>
  <listitem>
  <para>
- packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="control"/> ), and
+ packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="control"/>), and
  </para>
  </listitem>
  <listitem>
  <para>
- packages listed in the <literal>Build-Depends-indep</literal> field (see <xref linkend="control"/> ).
+ packages listed in the <literal>Build-Depends-indep</literal> field (see <xref linkend="control"/>).
  </para>
  </listitem>
  </itemizedlist>
-Line 3767 
 create and sign the upload <filename>.ch
+Line 3751 
 create and sign the upload <filename>.ch
  The only input that will be required of you is your GPG secret pass phrase,
  twice.
  <footnote><para>
- This GPG key must be signed by the Debian developer to get connected to the web
+ This GPG key must be signed by a Debian developer to get connected to the web
- of trust and must be registerd to <ulink url="&keyring;">the Debian
+ of trust and must be registered to <ulink url="&keyring;">the Debian
  keyring</ulink>.  This enables your uploaded packages to be accepted to the
  Debian archives.  See
  <ulink url="&keycreate;">Creating a new GPG key</ulink> and
-Line 3887 
 the <systemitem role="package">build-ess
+Line 3871 
 the <systemitem role="package">build-ess
  </listitem>
  <listitem>
  <para>
- packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="control"/> ).
+ packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="control"/>).
  </para>
  </listitem>
  </itemizedlist>
-Line 3935 
 This is why you see your package for oth
+Line 3919 
 This is why you see your package for oth
  </para>
  <para>
  Although packages listed in the <literal>Build-Depends-indep</literal> field
- are required to be installed for the normal packaging by us (see <xref linkend="completebuild"/> ), they are not required to be installed for the
+ are required to be installed for the normal packaging by us (see <xref linkend="completebuild"/>), they are not required to be installed for the
  autobuilder system since it build only architecture dependent binary packages.
  <footnote><para> Unlike under the <systemitem role="package">pbuilder</systemitem> package, the <command>chroot</command>
  environment under the <systemitem role="package">sbuild</systemitem> package
-Line 3944 
 many packages installed.  </para> </foot
+Line 3928 
 many packages installed.  </para> </foot
  packaging and autobuilder situation dictates whether you record such required
  packages in the <literal>Build-Depends</literal> or
  <literal>Build-Depends-indep</literal> fields of the
- <filename>debian/control</filename> file (see <xref linkend="control"/> ).
+ <filename>debian/control</filename> file (see <xref linkend="control"/>).
  </para>
  </section>
  <section id="option-sa"><title>Including <filename>orig.tar.gz</filename> for upload</title>
-Line 4259 
 All <emphasis>maintainer scripts</emphas
+Line 4243 
 All <emphasis>maintainer scripts</emphas
  <filename>preinst</filename>, <filename>prerm</filename>,
  <filename>postinst</filename>, and <filename>postrm</filename> files, are
  non-trivial unless they are auto-generated by the <systemitem role="package">debhelper</systemitem> programs.  So do not use them if you are
- a novice maintainer (see <xref linkend="maintscripts"/> ).
+ a novice maintainer (see <xref linkend="maintscripts"/>).
  </para>
  <para>
  If the package makes use of these non-trivial <emphasis>maintainer
-Line 4340 
 file.  The <command>lintian</command> co
+Line 4324 
 file.  The <command>lintian</command> co
  for many common packaging errors.  <footnote><para> You do not need to provide
  the <command>lintian</command> option <literal>-i -I --show-overrides</literal>
  if you customized <filename>/etc/devscripts.conf</filename> or
- <filename>~/.devscripts</filename> as described in <xref linkend="debuild"/> .
+ <filename>~/.devscripts</filename> as described in <xref linkend="debuild"/>.
  </para> </footnote>
  </para>
  <screen>
-Line 4384 
 error.
+Line 4368 
 error.
  <para>
  For warnings, tune the package to avoid them or verify that the warnings are
  spurious.  If spurious, set the <filename>lintian-overrides</filename> files as
- described in <xref linkend="lintian"/> .
+ described in <xref linkend="lintian"/>.
  </para>
  <para>
  Note that you can build the package with <command>dpkg-buildpackage</command>
-Line 4469 
 a public archive to share it.
+Line 4453 
 a public archive to share it.
  <para>
  Once you become an official developer,
  <footnote><para>
- See <xref linkend="debiandeveloper"/>.
+ See <xref linkend="socialdynamism"/>.
  </para></footnote>
  you can upload the package to the Debian archive.
  <footnote><para>
- There are publically accessible archives such as <ulink url="&mentors-dn;"/>
+ There are publicly accessible archives such as <ulink url="&mentors-dn;"/>
  which work almost the same way as Debian archive and provide upload area for
- the non-DD.  You can set up an equivqlent archive by yourself using tools
+ the non-DD.  You can set up an equivalent archive by yourself using tools
  listed at <ulink url="&deb-archive;"/>.  So this section is useful for the
  non-DD, too.
  </para></footnote>
-Line 4668 
 Repeat what you did in the above to fix
+Line 4652 
 Repeat what you did in the above to fix
  </listitem>
  <listitem>
  <para>
- Repeat what you did in <xref linkend="completebuild"/> , <xref linkend="checkit"/> , and <xref linkend="upload"/> .  The difference is that
+ Repeat what you did in <xref linkend="completebuild"/>, <xref linkend="checkit"/>, and <xref linkend="upload"/>.  The difference is that
  this time, the original source archive won't be included, as it hasn't been
  changed and it already exists in the Debian archive.
  </para>
-Line 4830 
 $ dch
+Line 4814 
 $ dch
  ... document changes made
  </screen>
  <para>
- If you set up a <filename>debian/watch</filename> file as described in <xref linkend="watch"/> , you can skip the <command>wget</command> command.  You
+ If you set up a <filename>debian/watch</filename> file as described in <xref linkend="watch"/>, you can skip the <command>wget</command> command.  You
  simply run <citerefentry> <refentrytitle>uscan</refentrytitle>
  <manvolnum>1</manvolnum> </citerefentry> in the
  <filename><replaceable>foo</replaceable>-<replaceable>oldversion</replaceable></filename>
-Line 4843 
 run the <command>uupdate</command> comma
+Line 4827 
 run the <command>uupdate</command> comma
  uupdate</literal> at the end of the URL.  </para> </footnote>
  </para>
  <para>
- You can release this updated source by repeating what you did in <xref linkend="completebuild"/> , <xref linkend="checkit"/> , and <xref linkend="upload"/> .
+ You can release this updated source by repeating what you did in <xref linkend="completebuild"/>, <xref linkend="checkit"/>, and <xref linkend="upload"/>.
  </para>
  </section>
  <section id="packagestyle"><title>Updating the packaging style</title>
-Line 4928 
 commands, remove such things and make it
+Line 4912 
 commands, remove such things and make it
  </listitem>
  </itemizedlist>
  <para>
- You need to do other tasks described in <xref linkend="newupstream"/> , too.
+ You need to do other tasks described in <xref linkend="newupstream"/>, too.
  </para>
  </section>
  <section id="reminders"><title>Reminders for updating packages</title>

 Legend:



Removed from v.8654
 


changed lines


 
Added in v.8705
 Legend:



Removed from v.8654
 


changed lines


 
Added in v.8705
-Removed from v.8654
+Added in v.8705

	ViewVC Help
Powered by ViewVC 1.1.5