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

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

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 8715 by osamu, Sat Apr 23 10:03:26 2011 UTC revision 8721 by osamu, Sun Apr 24 15:52:11 2011 UTC
# Line 105  takes many hours.  Make no mistake, for Line 105  takes many hours.  Make no mistake, for
105  need to be both technically competent and diligent.  need to be both technically competent and diligent.
106  </para>  </para>
107  <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  
 the next releases of that and maybe other packages later on.  
 </para>  
 <para>  
108  If you need some help on packaging, please read <xref linkend="helpme"/>.  If you need some help on packaging, please read <xref linkend="helpme"/>.
109  </para>  </para>
110  <para>  <para>
# Line 120  The translations may be available in pac Line 115  The translations may be available in pac
115  <systemitem role="package">maint-guide-es</systemitem>.  <systemitem role="package">maint-guide-es</systemitem>.
116  Please note that this documentation may be slightly outdated.  Please note that this documentation may be slightly outdated.
117  </para>  </para>
118    <para>
119    Since this is a tutorial, I choose to explain each detailed step for some
120    important topics.  Some of them may look irrelevant to you.  Please be patient.
121    I have also intentionally skipped some corner cases and provided only pointers
122    to keep this document simple.
123    </para>
124  <section id="socialdynamism"><title>Social dynamics of Debian</title>  <section id="socialdynamism"><title>Social dynamics of Debian</title>
125  <para>  <para>
126  Here are some observations of Debian's social dynamics, presented in the hope  Here are some observations of Debian's social dynamics, presented in the hope
# Line 421  those made for X11, also use these progr Line 422  those made for X11, also use these progr
422  <para>  <para>
423  The short descriptions that are given above only serve to introduce you to what  The short descriptions that are given above only serve to introduce you to what
424  each package does.  Before continuing please thoroughly read the documentation  each package does.  Before continuing please thoroughly read the documentation
425  of each program including ones installed through the package dependency such as  of each relevant program including ones installed through the package dependency such as
426  <command>make</command>, at least, for the standard usage.  It may seem like heavy  <command>make</command>, at least, for the standard usage.  It may seem like heavy
427  going now, but later on you'll be <emphasis>very</emphasis> glad you read it.  going now, but later on you'll be <emphasis>very</emphasis> glad you read it.
 </para>  
 <para>  
428  If you have specific questions later, I would suggest re-reading the documents  If you have specific questions later, I would suggest re-reading the documents
429  mentioned above.  Since this is a tutorial, I have intentionally skipped  mentioned above.
 details and provided only pointers to keep it simple.  
430  </para>  </para>
431  </section>  </section>
432  <section id="needdocs"><title>Documentation needed for development</title>  <section id="needdocs"><title>Documentation needed for development</title>
# Line 668  Debian Policy Manual: <ulink url="&polic Line 666  Debian Policy Manual: <ulink url="&polic
666  and is automatically assigned by the package build process.</para></footnote>  and is automatically assigned by the package build process.</para></footnote>
667  </para>  </para>
668  <para>  <para>
 You should chose the <emphasis role="strong">package name</emphasis>  
 which consists only of lower case letters (<literal>a-z</literal>), digits  
 (<literal>0-9</literal>), plus (<literal>+</literal>) and minus  
 (<literal>-</literal>) signs, and periods (<literal>.</literal>). They must be  
 at least two characters long and must start with an alphanumeric character.  
 </para>  
 <para>  
 You should use the <emphasis role="strong">upstream version</emphasis> and the  
 <emphasis role="strong">Debian revision</emphasis> which consists only of  
 alphanumerics (<literal>a-zA-Z0-9</literal>), plus (<literal>+</literal>),  
 tilde (<literal>~</literal>), and periods (<literal>.</literal>). They must  
 start with a digit (<literal>0-9</literal>).  <footnote><para>This stricter  
 rule should help you avoid confusing file names.</para></footnote>  
 </para>  
 <para>  
669  In the following, each step of this is explained with detailed examples.  In the following, each step of this is explained with detailed examples.
670  </para>  </para>
671  </section>  </section>
# Line 840  The program should not be a daemon, or g Line 823  The program should not be a daemon, or g
823  </listitem>  </listitem>
824  <listitem>  <listitem>
825  <para>  <para>
826  The program should be in binary executable form; libraries are harder to handle.  The program should be in the binary executable form; libraries are harder to handle.
827  </para>  </para>
828  </listitem>  </listitem>
829  <listitem>  <listitem>
# Line 910  case).  Place the downloaded archive in Line 893  case).  Place the downloaded archive in
893  xzf gentoo-0.9.12.tar.gz</literal>).  Make sure there are no warning  xzf gentoo-0.9.12.tar.gz</literal>).  Make sure there are no warning
894  messages, even <emphasis>irrelevant</emphasis> ones, because other  messages, even <emphasis>irrelevant</emphasis> ones, because other
895  people's unpacking tools may or may not ignore these anomalies, so they  people's unpacking tools may or may not ignore these anomalies, so they
896  may have problems unpacking them.  Your shell commandline may look  may have problems unpacking them.  Your shell command line may look
897  something like this:  something like this:
898  </para>  </para>
899  <screen>  <screen>
# Line 932  install to the <filename>/usr/local/bin< Line 915  install to the <filename>/usr/local/bin<
915  that, but more on that later in <xref linkend="destdir"/>).  that, but more on that later in <xref linkend="destdir"/>).
916  </para>  </para>
917  <para>  <para>
918    You should start packaging with a completely clean (pristine) source directory,
919    or simply with freshly unpacked sources.
920    </para>
921    </section>
922    <section id="simplemake"><title>Simple build systems</title>
923    <para>
924  Simple programs come with a <filename>Makefile</filename> and can  Simple programs come with a <filename>Makefile</filename> and can
925  be compiled just by invoking <literal>make</literal>.<footnote><para>  be compiled just by invoking <literal>make</literal>.<footnote><para>
926  Many modern programs come with a script <filename>configure</filename> which  Many modern programs come with a script <filename>configure</filename> which
# Line 955  all the installed files. Line 944  all the installed files.
944  <section id="portable"><title>Popular portable build systems</title>  <section id="portable"><title>Popular portable build systems</title>
945  <para>  <para>
946  A lot of free software programs are written in the <ulink url="&c-program;">C</ulink> and  A lot of free software programs are written in the <ulink url="&c-program;">C</ulink> and
947  <ulink url="&cxx;">C++</ulink> languages.  Many of  <ulink url="&cxx;">C++</ulink> languages.  Many of these use Autotools or
948  these use Autotools or CMake to make them portable across different platforms.  CMake to make them portable across different platforms.  These build tools need
949  These tools are used to generate the <filename>Makefile</filename> and other  to be used to generate the <filename>Makefile</filename> and other
950  required source files.  Then, such programs are built using the usual  required source files first.  Then, such programs are built using the usual
951  <literal>make; make install</literal>.  <literal>make; make install</literal>.
952  </para>  </para>
953  <para>  <para>
# Line 969  system comprising <ulink url="&autoconf; Line 958  system comprising <ulink url="&autoconf;
958  <ulink url="&gettext;">gettext</ulink>.  You can recognize  <ulink url="&gettext;">gettext</ulink>.  You can recognize
959  such sources by the <filename>configure.ac</filename>,  such sources by the <filename>configure.ac</filename>,
960  <filename>Makefile.am</filename>, and <filename>Makefile.in</filename> files.  <filename>Makefile.am</filename>, and <filename>Makefile.in</filename> files.
961  <footnote><para> See the <ulink url="&autotools-tutorial;">Autotools Tutorial</ulink>  <footnote><para>Autotools is too big to deal in this small tutorial. This
962  and <ulink url="&autotools-readme;"/>.  </para> </footnote>  section is mean to provide keywords and references only.  Please make sure to read the
963    <ulink url="&autotools-tutorial;">Autotools Tutorial</ulink> and
964    <ulink url="&autotools-readme;"/>, if you need to use it.</para></footnote>
965  </para>  </para>
966  <para>  <para>
967  The first step of the Autotools workflow is usually that upstream runs  The first step of the Autotools workflow is usually that upstream runs
# Line 997  files requires some knowledge of <comman Line 988  files requires some knowledge of <comman
988  The second step of the Autotools workflow is usually that the user obtains this  The second step of the Autotools workflow is usually that the user obtains this
989  distributed source and runs <literal>./configure &amp;&amp; make</literal> in  distributed source and runs <literal>./configure &amp;&amp; make</literal> in
990  the source directory to compile the program into a  the source directory to compile the program into a
991  <command><replaceable>binary</replaceable></command>.  <command><replaceable>binary</replaceable></command> executables.
992  </para>  </para>
993  <screen>  <screen>
994  Makefile.in -----+                +-&gt; Makefile -----+-&gt; make -&gt; <replaceable>binary</replaceable>  Makefile.in -----+                +-&gt; Makefile -----+-&gt; make -&gt; <replaceable>binary</replaceable>
# Line 1028  build system.  You can recognize such so Line 1019  build system.  You can recognize such so
1019  </section>  </section>
1020  <section id="namever"><title>Package name and version</title>  <section id="namever"><title>Package name and version</title>
1021  <para>  <para>
1022  You should start packaging with a completely clean (pristine) source directory,  If the upstream source comes as <filename>gentoo-0.9.12.tar.gz</filename>, you can
1023  or simply with freshly unpacked sources.  consider
1024    <emphasis role="strong">package name</emphasis> to be <literal>gentoo</literal> and
1025    <emphasis role="strong">upstream version</emphasis> to be <literal>0.9.12</literal>.
1026    These are used in the <filename>debian/changelog</filename> file described later in
1027    <xref linkend="changelog"/>, too.
1028    </para>
1029    <para>
1030    Although this simple approach works most of the times, you may need to adjust
1031    <emphasis role="strong">package name</emphasis> and
1032    <emphasis role="strong">upstream version</emphasis> by renaming the upstream
1033    source to follow the Debian policy and the existing convention.
1034  </para>  </para>
1035  <para>  <para>
1036  For the package to be built correctly, you must make the program's original  You must choose the <emphasis role="strong">package name</emphasis>
1037  name lowercase (if it isn't already), and you should move the source directory  to consist only of lower case letters (<literal>a-z</literal>), digits
1038  to  (<literal>0-9</literal>), plus (<literal>+</literal>) and minus
1039  <filename><replaceable>packagename</replaceable>-<replaceable>version</replaceable></filename>.  (<literal>-</literal>) signs, and periods (<literal>.</literal>). It must be
1040  </para>  at least two characters long, must start with an alphanumeric character, and
1041  <para>  must not be the same as existing ones.
1042  If the program name consists of more than one word, contract them to one word,  It is good idea to keep its length within 30 characters and should not exceed
1043  or make an abbreviation.  For example, a package of the program "John's little  40 characters.
1044  editor for X" might be named <systemitem role="package">johnledx</systemitem>, or  </para>
1045  <systemitem role="package">jle4x</systemitem>, or whatever you decide, as long  <!--
1046  as it's under some reasonable length limit, e.g. 20 characters.  Osamu's archive stat (2011-04-23, sid, kfreebsd-amd64):
1047  </para>  === stat for package name string length ===
1048  <para>  11 1947 36.9%   mode
1049  Also check for the exact version of the program (to be included in the package  14 1717 54.7%  50% median
1050  version).  If this piece of software is not numbered with versions like  23 611 91.0%   90%
1051  <literal>X.Y.Z</literal>, but with some kind of date, feel free to use that  32 89 99.0%    99%
1052  date as the version number, as long as newer version numbers will look larger.  41 12 99.9%    99.9%
1053  While it is best to use the same version numbering as upstream, if it is  52 1 100.0%
1054  in the format of <literal>09Oct23</literal> you may need to convert it to  Previous 20 chars is becoming too short for 17% of packages
1055  <literal>YYYYMMDD</literal> format, which would be <literal>20091023</literal>,  Default aptitude setting display up to 30 chars (98.3%).
1056  to ensure that <command>dpkg</command> sees later versions as  -->
1057  upgrades.<footnote><para> Version strings can be compared with <literal>dpkg  <para>
1058  --compare-versions <replaceable>ver1</replaceable>  If upstream source uses generic words such as <literal>test-suite</literal> as
1059  <replaceable>op</replaceable> <replaceable>ver2</replaceable></literal>.  See  its name, it is good idea to rename it not to contaminate name space for the
1060  <citerefentry> <refentrytitle>dpkg</refentrytitle> <manvolnum>1</manvolnum>  package name and to identify its contents explicitly.
1061  </citerefentry>.  </para> </footnote>  <footnote><para>If you follow the
1062    <ulink url="&devref-newpackage;">Developer's Reference 5.1. 'New packages'</ulink>,
1063    the ITP process will usually catch this kind of issues.</para></footnote>.
1064    </para>
1065    <para>
1066    You should choose the <emphasis role="strong">upstream version</emphasis>
1067    to consist only of
1068    alphanumerics (<literal>0-9A-Za-z</literal>), plus (<literal>+</literal>),
1069    tilde (<literal>~</literal>), and periods (<literal>.</literal>). It must
1070    start with a digit (<literal>0-9</literal>).  <footnote><para>This stricter
1071    rule should help you avoid confusing file names.</para></footnote>
1072    It is good idea to keep its length within 8 characters if possible.
1073  </para>  </para>
1074    <!--
1075    Osamu's archive stat (2011-04-23, sid, kfreebsd-amd64):
1076    === stat for upstream version string length ===
1077    5 9765 60.2%  50% median and mode
1078    6 3765 73.3%
1079    7 2789 82.9%
1080    8 1158 86.9%
1081    9 501 88.6%
1082    10 773 91.3%  90%
1083    18 55 99.1%   99%
1084    27 11 99.9%    99.9
1085    35 6 100.0%
1086    === stat for debian revision string length ===
1087    1 22556 83.3%  50% median and mode
1088    2 1106 87.2%
1089    3 1312 91.7%   90%
1090    4 2127 99.1%   99%
1091    7 14 99.9%     99.9%
1092    
1093    aptitude display 10 = 8char for up + 1char (for -) + 1char for deb
1094    90chars as max for file name of binary debs (package+up+deb+arch+.deb)
1095    -->
1096    <para>
1097    If the upstream software does not use normal version system like
1098    <literal>2.30.32</literal> but uses some kind of date such as
1099    <literal>09Oct23</literal>, a random codename string or a VCS hush value as a part
1100    of version, make sure to remove them from the
1101    <emphasis role="strong">upstream version</emphasis>.  Such information can be
1102    recorded in the <filename>debian/changelog</filename> file.  If you need to
1103    invent a version string, use the <literal>YYYYMMDD</literal> format such as
1104    <literal>20110429</literal> as upstream version.  This ensures that
1105    <command>dpkg</command> properly sees later versions as upgrades.
1106    </para>
1107    <para>
1108    Version strings can be compared with <citerefentry> <refentrytitle>dpkg</refentrytitle> <manvolnum>1</manvolnum> </citerefentry> as the following.
1109    </para>
1110    <screen>
1111     $ dpkg --compare-versions <replaceable>ver1</replaceable> <replaceable>op</replaceable> <replaceable>ver2</replaceable>
1112    </screen>
1113    <para>
1114    The version comparison rule can be summarized as the folowing.
1115    </para>
1116    <itemizedlist>
1117    <listitem><para>The strings are compared from the head to the tail.</para></listitem>
1118    <listitem><para>Alphabets are larger than numbers.</para></listitem>
1119    <listitem><para>Numbers are compared as the integer.</para></listitem>
1120    <listitem><para>Alphabets are compared in the ASCII code order.</para></listitem>
1121    <listitem><para>There are some special rules for periods (<literal>.</literal>), plus (<literal>+</literal>) and tilde (<literal>~</literal>) as the followings.</para>
1122      <para>
1123      <literal>0.0</literal> &lt;
1124      <literal>0.5</literal> &lt;
1125      <literal>0.10</literal> &lt;
1126      <literal>0.99</literal> &lt;
1127      <literal>1</literal> &lt;
1128      <literal>1.0~rc1</literal> &lt;
1129      <literal>1.0</literal> &lt;
1130      <literal>1.0+b1</literal> &lt;
1131      <literal>1.0+nmu1</literal> &lt;
1132      <literal>1.1</literal> &lt;
1133      <literal>2.0</literal>
1134      </para>
1135    </listitem>
1136    </itemizedlist>
1137  <para>  <para>
1138  Some programs won't be numbered at all, in which case you should contact the  One of the tricky case happens when the upstream releases
1139  upstream maintainer to see if they've got some other revision-tracking method.  <filename>gentoo-0.9.12-ReleaseCandidate-99.tar.gz</filename> as the
1140    pre-release of <filename>gentoo-0.9.12.tar.gz</filename>.  You need to make
1141    sure that the upgrade works properly by renaming the upstream source to
1142    <filename>gentoo-0.9.12~rc99.tar.gz</filename>.
1143  </para>  </para>
1144  </section>  </section>
1145  <section id="dh-make"><title>Initial Debian package</title>  <section id="dh-make"><title>Initial Debian package</title>
1146  <para>  <para>
1147  Set up the shell environment variables <literal>$DEBEMAIL</literal> and  Set up the shell environment variables <literal>$DEBEMAIL</literal> and
1148  <literal>$DEBFULLNAME</literal> so that various Debian maintenance  <literal>$DEBFULLNAME</literal> so that various Debian maintenance
1149  tools recognize your email address and name to use for packages.<footnote><para> The  tools recognize your email address and name to use for packages. <footnote><para> The
1150  following text assumes you are using Bash as your login shell.  If you use  following text assumes you are using Bash as your login shell.  If you use
1151  some other login shell such as Z shell, use their corresponding  some other login shell such as Z shell, use their corresponding
1152  configuration files instead of <filename>~/.bashrc</filename>. </para> </footnote>.  configuration files instead of <filename>~/.bashrc</filename>. </para> </footnote>
1153  </para>  </para>
1154  <screen>  <screen>
1155  $ cat &gt;&gt;~/.bashrc &lt;&lt;EOF  $ cat &gt;&gt;~/.bashrc &lt;&lt;EOF
# Line 1102  provided by the upstream for your Debian Line 1180  provided by the upstream for your Debian
1180  </para>  </para>
1181  <para>  <para>
1182  You should see some output asking you what sort of package you want  You should see some output asking you what sort of package you want
1183  to create.  Gentoo is a single binary package - it creates only one binary, and  to create.  Gentoo is a single-binary package - it creates only one binary package, i.e,
1184  thus one <filename>.deb</filename> file - so we will select the first option  one <filename>.deb</filename> file - so we will select the first option
1185  (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
1186  confirm by pressing <literal><replaceable>ENTER</replaceable></literal>.  confirm by pressing <literal><replaceable>ENTER</replaceable></literal>.
1187  <footnote><para> There are several choices here: <literal>s</literal> for Single  <footnote><para> There are several choices here: <literal>s</literal> for
1188  binary, <literal>i</literal> for arch-Independent, <literal>m</literal> for  Single-binary package, <literal>i</literal> for arch-Independent package, <literal>m</literal> for
1189  Multiple binary, <literal>l</literal> for Library, <literal>k</literal> for  Multiple-binary packages, <literal>l</literal> for Library package, <literal>k</literal> for
1190  Kernel module, <literal>n</literal> for kernel patch, and <literal>b</literal>  Kernel module package, <literal>n</literal> for kernel patch package, and <literal>b</literal>
1191  for <systemitem role="package">cdbs</systemitem>.  This document focuses on the  for <systemitem role="package">cdbs</systemitem> package.  This document focuses on the
1192  use of the <command>dh</command> command (from the package  use of the <command>dh</command> command (from the package
1193  <systemitem role="package">debhelper</systemitem>) to create a single-binary package,  <systemitem role="package">debhelper</systemitem>) to create a single-binary package,
1194  but also touches on how to use it for arch-independent or  but also touches on how to use it for arch-independent or
# Line 1166  packages, e.g.: Line 1244  packages, e.g.:
1244  <itemizedlist>  <itemizedlist>
1245  <listitem>  <listitem>
1246  <para>  <para>
1247  multiple binary packages;  multiple-binary packages;
1248  </para>  </para>
1249  </listitem>  </listitem>
1250  <listitem>  <listitem>
# Line 1395  from the <command>dh_auto_configure</com Line 1473  from the <command>dh_auto_configure</com
1473  options including <literal>--prefix=/usr</literal>.  </para> </footnote>:  options including <literal>--prefix=/usr</literal>.  </para> </footnote>:
1474  </para>  </para>
1475  <screen>  <screen>
1476  # Where to put binary on 'make install'?  # Where to put binary executables on 'make install'?
1477  BIN     = /usr/local/bin  BIN     = /usr/local/bin
1478  # Where to put icons on 'make install'?  # Where to put icons on 'make install'?
1479  ICONS   = /usr/local/share/gentoo  ICONS   = /usr/local/share/gentoo
# Line 1406  As explained above, that directory hiera Line 1484  As explained above, that directory hiera
1484  Debian, so change those paths to:  Debian, so change those paths to:
1485  </para>  </para>
1486  <screen>  <screen>
1487  # Where to put binary on 'make install'?  # Where to put binary executables on 'make install'?
1488  BIN     = $(DESTDIR)/usr/bin  BIN     = $(DESTDIR)/usr/bin
1489  # Where to put icons on 'make install'?  # Where to put icons on 'make install'?
1490  ICONS   = $(DESTDIR)/usr/share/gentoo  ICONS   = $(DESTDIR)/usr/share/gentoo
# Line 1418  documentation, etc. are specified in the Line 1496  documentation, etc. are specified in the
1496  your package.  your package.
1497  </para>  </para>
1498  <para>  <para>
1499  So, we should install the binary in <filename>/usr/bin</filename> instead of  So, we should install binary executables in <filename>/usr/bin</filename> instead of
1500  <filename>/usr/local/bin</filename>, the manual page in  <filename>/usr/local/bin</filename>, the manual page in
1501  <filename>/usr/share/man/man1</filename> instead of  <filename>/usr/share/man/man1</filename> instead of
1502  <filename>/usr/local/man/man1</filename>, and so on.  Notice how there's no manual  <filename>/usr/local/man/man1</filename>, and so on.  Notice how there's no manual
# Line 1449  $ sed -i -e 's#usr/local/lib#usr/lib#g' Line 1527  $ sed -i -e 's#usr/local/lib#usr/lib#g'
1527        $(find . -type f -name '*.[c|h]')        $(find . -type f -name '*.[c|h]')
1528  </screen>  </screen>
1529  <para>  <para>
1530  If you want to confirm each substituion instead, this can be done interactively as follows:  If you want to confirm each substitution instead, this can be done interactively as follows:
1531  </para>  </para>
1532  <screen>  <screen>
1533  $ vim '+argdo %s#usr/local/lib#usr/lib#gce|update' +q \  $ vim '+argdo %s#usr/local/lib#usr/lib#gce|update' +q \
# Line 1707  Build-Conflicts-Indep'</ulink>.</para></ Line 1785  Build-Conflicts-Indep'</ulink>.</para></
1785  <systemitem role="package">build-essential</systemitem> package are implied.  If you need  <systemitem role="package">build-essential</systemitem> package are implied.  If you need
1786  to have other tools to build your package, you should add them to these fields.  to have other tools to build your package, you should add them to these fields.
1787  Multiple entries are separated with commas; read on for the explanation of  Multiple entries are separated with commas; read on for the explanation of
1788  binary dependencies to find out more about the syntax of these lines.  binary package dependencies to find out more about the syntax of these lines.
1789  </para>  </para>
1790  <itemizedlist>  <itemizedlist>
1791  <listitem>  <listitem>
# Line 3226  the <filename>docs</filename> file and n Line 3304  the <filename>docs</filename> file and n
3304  This <filename>install</filename> file has one line per file installed, with  This <filename>install</filename> file has one line per file installed, with
3305  the name of the file (relative to the top build directory) then a space then  the name of the file (relative to the top build directory) then a space then
3306  the installation directory (relative to the install directory).  One example of  the installation directory (relative to the install directory).  One example of
3307  where this is used is where a binary is forgotten to be installed, the  this is when a binary executable is forgotten to be installed, the
3308  <filename>install</filename> file would look like:  <filename>install</filename> file would look like:
3309  </para>  </para>
3310  <screen>  <screen>
3311  src/foo/mybin usr/bin  src/foo/mybin usr/bin
3312  </screen>  </screen>
3313  <para>  <para>
3314  This will mean when this package is installed, there will be a binary file  This will mean when this package is installed, there will be a binary executable
3315  <filename>/usr/bin/mybin</filename>.  <filename>/usr/bin/mybin</filename>.
3316  </para>  </para>
3317  <para>  <para>
# Line 3629  summary information concerning the switc Line 3707  summary information concerning the switc
3707  <filename>debian.tar.gz</filename> archive containing all files under the  <filename>debian.tar.gz</filename> archive containing all files under the
3708  <filename>debian</filename> directory.  This new format supports inclusion of  <filename>debian</filename> directory.  This new format supports inclusion of
3709  binary files such as PNG icons by the package maintainer without requiring  binary files such as PNG icons by the package maintainer without requiring
3710  tricks.  <footnote><para> Actually, this new format also supports multiple  tricks.  <footnote><para>Actually, this new format also supports multiple
3711  upstream tarballs and more compression methods.  These are beyond the scope of  upstream tarballs and more compression methods.  These are beyond the scope of
3712  this document.  </para> </footnote>  this document.</para> </footnote>
3713  </para>  </para>
3714  <para>  <para>
3715  When <command>dpkg-source</command> extracts a source package in <literal>3.0  When <command>dpkg-source</command> extracts a source package in <literal>3.0
Legend:
Removed from v.8715  
changed lines
  Added in v.8721
  ViewVC Help
Powered by ViewVC 1.1.5