Gecko [ ifk.uw.edu.pl ]

Name	Size	Permission
ch-basic_defs.en.html	34.93 KB	-rw-r--r--
ch-basic_defs.html	34.93 KB	-rw-r--r--
ch-choosing.en.html	44.66 KB	-rw-r--r--
ch-choosing.html	44.66 KB	-rw-r--r--
ch-compat.en.html	33.45 KB	-rw-r--r--
ch-compat.html	33.45 KB	-rw-r--r--
ch-contributing.en.html	27.15 KB	-rw-r--r--
ch-contributing.html	27.15 KB	-rw-r--r--
ch-customizing.en.html	37.07 KB	-rw-r--r--
ch-customizing.html	37.07 KB	-rw-r--r--
ch-faqinfo.en.html	26.29 KB	-rw-r--r--
ch-faqinfo.html	26.29 KB	-rw-r--r--
ch-ftparchives.en.html	39.02 KB	-rw-r--r--
ch-ftparchives.html	39.02 KB	-rw-r--r--
ch-getting.en.html	28.45 KB	-rw-r--r--
ch-getting.html	28.45 KB	-rw-r--r--
ch-kernel.en.html	25.53 KB	-rw-r--r--
ch-kernel.html	25.53 KB	-rw-r--r--
ch-nexttime.en.html	27.64 KB	-rw-r--r--
ch-nexttime.html	27.64 KB	-rw-r--r--
ch-pkg_basics.en.html	48.23 KB	-rw-r--r--
ch-pkg_basics.html	48.23 KB	-rw-r--r--
ch-pkgtools.en.html	41.75 KB	-rw-r--r--
ch-pkgtools.html	41.75 KB	-rw-r--r--
ch-redistrib.en.html	25.88 KB	-rw-r--r--
ch-redistrib.html	25.88 KB	-rw-r--r--
ch-software.en.html	34.18 KB	-rw-r--r--
ch-software.html	34.18 KB	-rw-r--r--
ch-support.en.html	34.63 KB	-rw-r--r--
ch-support.html	34.63 KB	-rw-r--r--
ch-uptodate.en.html	32.38 KB	-rw-r--r--
ch-uptodate.html	32.38 KB	-rw-r--r--
debian-faq.en.pdf.gz	300.34 KB	-rw-r--r--
debian-faq.en.ps.gz	245.87 KB	-rw-r--r--
debian-faq.en.txt.gz	58.04 KB	-rw-r--r--
debian-faq.pdf.gz	300.34 KB	-rw-r--r--
debian-faq.ps.gz	245.87 KB	-rw-r--r--
debian-faq.txt.gz	58.04 KB	-rw-r--r--
footnotes.en.html	25.56 KB	-rw-r--r--
footnotes.html	25.56 KB	-rw-r--r--
index.en.html	42.78 KB	-rw-r--r--
index.html	42.78 KB	-rw-r--r--

Code Editor : ch-pkg_basics.en.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">

<html>

<head>

<title>The Debian GNU/Linux FAQ - Basics of the Debian package management system</title>

</head>

<body>

[ <a href="ch-ftparchives.en.html">previous</a> ]
[ <a href="index.en.html#contents">Contents</a> ]
[ <a href="ch-basic_defs.en.html">1</a> ]
[ <a href="ch-getting.en.html">2</a> ]
[ <a href="ch-choosing.en.html">3</a> ]
[ <a href="ch-compat.en.html">4</a> ]
[ <a href="ch-software.en.html">5</a> ]
[ <a href="ch-ftparchives.en.html">6</a> ]
[ 7 ]
[ <a href="ch-pkgtools.en.html">8</a> ]
[ <a href="ch-uptodate.en.html">9</a> ]
[ <a href="ch-kernel.en.html">10</a> ]
[ <a href="ch-customizing.en.html">11</a> ]
[ <a href="ch-support.en.html">12</a> ]
[ <a href="ch-contributing.en.html">13</a> ]
[ <a href="ch-redistrib.en.html">14</a> ]
[ <a href="ch-nexttime.en.html">15</a> ]
[ <a href="ch-faqinfo.en.html">16</a> ]
[ <a href="ch-pkgtools.en.html">next</a> ]

<hr>

<h1>
The Debian GNU/Linux FAQ
 Chapter 7 - Basics of the Debian package management system
</h1>

<hr>

This chapter touches on some lower level internals of Debian package
management. If you're interested mainly in usage of the relevant
tools, skip to chapters <a href="ch-pkgtools.en.html">The Debian package
management tools, Chapter 8</a> and/or <a href="ch-uptodate.en.html">Keeping
your Debian system up-to-date, Chapter 9</a>.

<hr>

<h2 id="s-package">7.1 What is a Debian package?</h2>

Packages generally contain all of the files necessary to implement a set of
related commands or features. There are two types of Debian packages:

<ul>
<li>

Binary packages, which contain executables, configuration files,
man/info pages, copyright information, and other documentation. These packages
are distributed in a Debian-specific archive format (see <a
href="#s-deb-format">What is the format of a Debian binary package?, Section
7.2</a>); they are usually characterized by having a '.deb' file extension.
Binary packages can be unpacked using the Debian utility <samp>dpkg</samp>
(possibly via a frontend like <code>aptitude</code>); details are given in its
manual page.

</li>
</ul>
<ul>
<li>

Source packages, which consist of a <samp>.dsc</samp> file describing
the source package (including the names of the following files), a
<samp>.orig.tar.gz</samp> file that contains the original unmodified source in
gzip-compressed tar format and usually a <samp>.diff.gz</samp> file that
contains the Debian-specific changes to the original source. The utility
<samp>dpkg-source</samp> packs and unpacks Debian source archives; details are
provided in its manual page. (The program <code>apt-get</code> can be used as
a frontend for <samp>dpkg-source</samp>.)

</li>
</ul>

Installation of software by the package system uses &quot;dependencies&quot;
which are carefully designed by the package maintainers. These dependencies
are documented in the <samp>control</samp> file associated with each package.
For example, the package containing the GNU C compiler (<code>gcc</code>)
&quot;depends&quot; on the package <code>binutils</code> which includes the
linker and assembler. If a user attempts to install <code>gcc</code> without
having first installed <code>binutils</code>, the package management system
(dpkg) will send an error message that it also needs <code>binutils</code>, and
stop installing <code>gcc</code>. (However, this facility can be overridden by
the insistent user, see <code>dpkg(8)</code>.) See more in <a
href="#s-depends">What is meant by saying that a package Depends,
Recommends, Suggests, Conflicts, Replaces,
Breaks or Provides another package?, Section 7.9</a> below.

Debian's packaging tools can be used to:

<ul>
<li>

manipulate and manage packages or parts of packages,

</li>
</ul>
<ul>
<li>

administer local overrides of files in a package,

</li>
</ul>
<ul>
<li>

aid developers in the construction of package archives, and

</li>
</ul>
<ul>
<li>

aid users in the installation of packages which reside on a remote FTP site.

</li>
</ul>

<hr>

<h2 id="s-deb-format">7.2 What is the format of a Debian binary package?</h2>

A Debian &quot;package&quot;, or a Debian archive file, contains the executable
files, libraries, and documentation associated with a particular suite of
program or set of related programs. Normally, a Debian archive file has a
filename that ends in <samp>.deb</samp>.

The internals of this Debian binary packages format are described in the
<code>deb(5)</code> manual page. This internal format is subject to change
(between major releases of Debian GNU/Linux), therefore please always use
<code>dpkg-deb(1)</code> if you need to do lowlevel manipulations on
<samp>.deb</samp> files.

<hr>

<h2 id="s-pkgname">7.3 Why are Debian package file names so long?</h2>

The Debian binary package file names conform to the following convention:
&lt;foo&gt;_&lt;VersionNumber&gt;-&lt;DebianRevisionNumber&gt;_&lt;DebianArchitecture&gt;.deb

Note that <samp>foo</samp> is supposed to be the package name. Checking the
package name associated with a particular Debian archive file (.deb file) can
be done in one of these ways:

<ul>
<li>

inspect the &quot;Packages&quot; file in the directory where it was stored at a
Debian FTP archive site. This file contains a stanza describing each package;
the first field in each stanza is the formal package name.

</li>
</ul>
<ul>
<li>

use the command <samp>dpkg --info foo_VVV-RRR_AAA.deb</samp> (where VVV, RRR
and AAA are the version, revision and architecture of the package in question,
respectively). This displays, among other things, the package name
corresponding to the archive file being unpacked.

</li>
</ul>

The <samp>VVV</samp> component is the version number specified by the upstream
developer. There are no standards in place here, so the version number may
have formats as different as &quot;19990513&quot; and &quot;1.3.8pre1&quot;.

The <samp>RRR</samp> component is the Debian revision number, and is specified
by the Debian developer (or an individual user if he chooses to build the
package himself). This number corresponds to the revision level of the Debian
package, thus, a new revision level usually signifies changes in the Debian
Makefile (<samp>debian/rules</samp>), the Debian control file
(<samp>debian/control</samp>), the installation or removal scripts
(<samp>debian/p*</samp>), or in the configuration files used with the package.

The <samp>AAA</samp> component identifies the processor for which the package
was built. This is commonly <samp>amd64</samp>, which refers to AMD64, Intel
64 or VIA Nano chips. For other possibilities review Debian's FTP directory
structure at <a href="ch-ftparchives.en.html#s-dirtree">What are all those
directories at the Debian FTP archives?, Section 6.7</a>. For details, see the
description of &quot;Debian architecture&quot; in the manual page
<code>dpkg-architecture(1)</code>.

<hr>

<h2 id="s-controlfile">7.4 What is a Debian control file?</h2>

Specifics regarding the contents of a Debian control file are provided in the
Debian Policy Manual, section 5, see <a
href="ch-support.en.html#s-debiandocs">What other documentation exists on and
for a Debian system?, Section 12.1</a>.

Briefly, a sample control file is shown below for the Debian package hello:

<pre>
 Package: hello
 Version: 2.9-2+deb8u1
 Architecture: amd64
 Maintainer: Santiago Vila &lt;sanvila@debian.org&gt;
 Installed-Size: 145
 Depends: libc6 (&gt;= 2.14)
 Conflicts: hello-traditional
 Breaks: hello-debhelper (&lt;&lt; 2.9)
 Replaces: hello-debhelper (&lt;&lt; 2.9), hello-traditional
 Section: devel
 Priority: optional
 Homepage: http://www.gnu.org/software/hello/
 Description: example package based on GNU hello
 The GNU hello program produces a familiar, friendly greeting. It
 allows non-programmers to use a classic computer science tool which
 would otherwise be unavailable to them.
 .
 Seriously, though: this is an example of how to do a Debian package.
 It is the Debian version of the GNU Project's `hello world' program
 (which is itself an example for the GNU Project).
</pre>

The Package field gives the package name. This is the name by which the
package can be manipulated by the package tools, and usually similar to but not
necessarily the same as the first component string in the Debian archive file
name.

The Version field gives both the upstream developer's version number and (in
the last component) the revision level of the Debian package of this program as
explained in <a href="#s-pkgname">Why are Debian package file names so long?,
Section 7.3</a>.

The Architecture field specifies the chip for which this particular binary was
compiled.

The Depends field gives a list of packages that have to be installed in order
to install this package successfully.

The Installed-Size indicates how much disk space the installed package will
consume. This is intended to be used by installation front-ends in order to
show whether there is enough disk space available to install the program.

The Section line gives the &quot;section&quot; where this Debian package is
stored at the Debian FTP sites.

The Priority indicates how important is this package for installation, so that
semi-intelligent software like apt or aptitude can sort the package into a
category of e.g. packages optionally installed. See <a
href="#s-priority">What is an Essential, Required,
Important, Standard, Optional, or Extra
package?, Section 7.7</a>.

The Maintainer field gives the e-mail address of the person who is currently
responsible for maintaining this package.

The Description field gives a brief summary of the package's features.

For more information about all possible fields a package can have, please see
the Debian Policy Manual, section 5, &quot;Control files and their
fields&quot;, see <a href="ch-support.en.html#s-debiandocs">What other
documentation exists on and for a Debian system?, Section 12.1</a>.

<hr>

<h2 id="s-conffile">7.5 What is a Debian conffile?</h2>

Conffiles is a list of configuration files (usually placed in
<samp>/etc</samp>) that the package management system will not overwrite when
the package is upgraded. This ensures that local values for the contents of
these files will be preserved, and is a critical feature enabling the in-place
upgrade of packages on a running system.

To determine exactly which files are preserved during an upgrade, run:

<pre>
 dpkg --status package
</pre>

And look under &quot;Conffiles:&quot;.

<hr>

<h2 id="s-maintscripts">7.6 What is a Debian preinst, postinst, prerm, and postrm script?</h2>

These files are executable scripts which are automatically run before or after
a package is installed or removed. Along with a file named
<samp>control</samp>, all of these files are part of the &quot;control&quot;
section of a Debian archive file.

The individual files are:

<dl>
<dt>preinst</dt>
<dd>

This script is executed before the package it belongs to is unpacked from its
Debian archive (&quot;.deb&quot;) file. Many 'preinst' scripts stop services
for packages which are being upgraded until their installation or upgrade is
completed (following the successful execution of the 'postinst' script).

</dd>
</dl>
<dl>
<dt>postinst</dt>
<dd>

This script typically completes any required configuration of the package
<samp>foo</samp> once <samp>foo</samp> has been unpacked from its Debian
archive (&quot;.deb&quot;) file. Often, 'postinst' scripts ask users for
input, and/or warn them that if they accept default values, they should
remember to go back and re-configure that package as needed. Many 'postinst'
scripts then execute any commands necessary to start or restart a service once
a new package has been installed or upgraded.

</dd>
</dl>
<dl>
<dt>prerm</dt>
<dd>

This script typically stops any daemons which are associated with a package.
It is executed before the removal of files associated with the package.

</dd>
</dl>
<dl>
<dt>postrm</dt>
<dd>

This script typically modifies links or other files associated with
<samp>foo</samp>, and/or removes files created by the package. (Also see <a
href="#s-virtual">What is a Virtual Package?, Section 7.8</a>.)

</dd>
</dl>

Currently all of the control files can be found in the directory
<samp>/var/lib/dpkg/info</samp>. The files relevant to package
<samp>foo</samp> begin with the name &quot;foo&quot; and have file extensions
of &quot;preinst&quot;, &quot;postinst&quot;, etc., as appropriate. The file
<samp>foo.list</samp> in that directory lists all of the files that were
installed with the package <samp>foo</samp>. (Note that the location of these
files is a dpkg internal; you should not rely on it.)

<hr>

<h2 id="s-priority">7.7 What is an Essential, Required, Important, Standard, Optional, or Extra package?</h2>

Each Debian package is assigned a priority by the distribution
maintainers, as an aid to the package management system. The priorities are:

<ul>
<li>

Required: packages that are necessary for the proper
functioning of the system.

This includes all tools that are necessary to repair system defects. You must
not remove these packages or your system may become totally broken and you may
probably not even be able to use dpkg to put things back. Systems with only
the Required packages are probably unusable, but they do have enough
functionality to allow the sysadmin to boot and install more software.

</li>
</ul>
<ul>
<li>

Important packages should be found on any Unix-like system.

Other packages which the system will not run well or be usable without will be
here. This does NOT include Emacs or X or TeX or any other large
application. These packages only constitute the bare infrastructure.

</li>
</ul>
<ul>
<li>

Standard packages are standard on any Linux system, including
a reasonably small but not too limited character-mode system. Tools are
included to be able to send e-mail (with mutt) and download files from FTP
servers.

This is what will be installed by default if users do not select anything else.
It does not include many large applications, but it does include the Python
interpreter and some server software like OpenSSH (for remote administration)
and Exim (for mail delivery, although it can be configured for local delivery
only). It also includes some common generic documentation that most users will
find helpful.

</li>
</ul>
<ul>
<li>

Optional packages include all those that you might reasonably
want to install if you do not know what they are, or that do not have
specialized requirements.

This includes X, a full TeX distribution, and lots of applications.

</li>
</ul>
<ul>
<li>

Extra: packages that either conflict with others with higher
priorities, are only likely to be useful if you already know what they are, or
have specialized requirements that make them unsuitable for
&quot;Optional&quot;.

</li>
</ul>

If you do a default Debian installation all the packages of priority
Standard or higher will be installed in your system. If you
select pre-defined tasks you will get lower priority packages too.

Additionally, some packages are marked as Essential since they
are absolutely necessary for the proper functioning of the system. The package
management tools will refuse to remove these.

<hr>

<h2 id="s-virtual">7.8 What is a Virtual Package?</h2>

A virtual package is a generic name that applies to any one of a group of
packages, all of which provide similar basic functionality. For example, both
the <samp>konqueror</samp> and <samp>firefox-esr</samp> programs are web
browsers, and should therefore satisfy any dependency of a program that
requires a web browser on a system, in order to work or to be useful. They are
therefore both said to provide the &quot;virtual package&quot; called
<samp>www-browser</samp>.

Similarly, <samp>exim4</samp> and <samp>sendmail</samp> both provide the
functionality of a mail transport agent. They are therefore said to provide
the virtual package &quot;mail-transport-agent&quot;. If either one is
installed, then any program depending on the installation of a
<samp>mail-transport-agent</samp> will be satisfied by the presence of this
virtual package.

Debian provides a mechanism so that, if more than one package which provide the
same virtual package is installed on a system, then system administrators can
set one as the preferred package. The relevant command is
<samp>update-alternatives</samp>, and is described further in <a
href="ch-customizing.en.html#s-diverse">Some users like mawk, others like gawk;
some like vim, others like elvis; some like trn, others like tin; how does
Debian support diversity?, Section 11.11</a>.

<hr>

<h2 id="s-depends">7.9 What is meant by saying that a package Depends, Recommends, Suggests, Conflicts, Replaces, Breaks or Provides another package?</h2>

The Debian package system has a range of package &quot;dependencies&quot; which
are designed to indicate (in a single flag) the level at which Program A can
operate independently of the existence of Program B on a given system:

<ul>
<li>

Package A depends on Package B if B absolutely must be installed in
order to run A. In some cases, A depends not only on B, but on a version of B.
In this case, the version dependency is usually a lower limit, in the sense
that A depends on any version of B more recent than some specified version.

</li>
</ul>
<ul>
<li>

Package A recommends Package B, if the package maintainer judges that
most users would not want A without also having the functionality provided by
B.

</li>
</ul>
<ul>
<li>

Package A suggests Package B if B contains files that are related to
(and usually enhance) the functionality of A.

</li>
</ul>
<ul>
<li>

Package A conflicts with Package B when A will not operate if B is
installed on the system. Most often, conflicts are cases where A contains
files which are an improvement over those in B. &quot;Conflicts&quot; are
often combined with &quot;replaces&quot;.

</li>
</ul>
<ul>
<li>

Package A replaces Package B when files installed by B are removed and
(in some cases) over-written by files in A.

</li>
</ul>
<ul>
<li>

Package A breaks Package B when both packages cannot be simultaneously
configured in a system. The package management system will refuse to install
one if the other one is already installed and configured in the system.

</li>
</ul>
<ul>
<li>

Package A provides Package B when all of the files and functionality
of B are incorporated into A. This mechanism provides a way for users with
constrained disk space to get only that part of package A which they really
need.

</li>
</ul>

More detailed information on the use of each of these terms can be found in the
Debian Policy manual, section 7.2, &quot;Binary Dependencies&quot;, see <a
href="ch-support.en.html#s-debiandocs">What other documentation exists on and
for a Debian system?, Section 12.1</a>.

<hr>

<h2 id="s-pre-depends">7.10 What is meant by Pre-Depends?</h2>

&quot;Pre-Depends&quot; is a special dependency. In the case of most packages,
<samp>dpkg</samp> will unpack the archive file of a package (i.e., its
<samp>.deb</samp> file) independently of whether or not the files on which it
depends exist on the system. Simplistically, unpacking means that
<samp>dpkg</samp> will extract the files from the archive file that were meant
to be installed on your file system, and put them in place. If those packages
depend on the existence of some other packages on your system,
<samp>dpkg</samp> will refuse to complete the installation (by executing its
&quot;configure&quot; action) until the other packages are installed.

However, for some packages, <samp>dpkg</samp> will refuse even to unpack them
until certain dependencies are resolved. Such packages are said to
&quot;Pre-depend&quot; on the presence of some other packages. The Debian
project provided this mechanism to support the safe upgrading of systems from
<samp>a.out</samp> format to <samp>ELF</samp> format, where the order
in which packages were unpacked was critical. There are other large upgrade
situations where this method is useful, e.g. the packages with the required
priority and their LibC dependency.

As before, more detailed information about this can be found in the Policy
manual.

<hr>

<h2 id="s-pkgstatus">7.11 What is meant by unknown, install, remove, purge and hold in the package status?</h2>

These &quot;want&quot; flags tell what the user wanted to do with a package (as
indicated by the user's direct invocations of
<samp>dpkg</samp>/<samp>apt</samp>/ <samp>aptitude</samp>).

Their meanings are:

<ul>
<li>

unknown - the user has never indicated whether the package is wanted.

</li>
</ul>
<ul>
<li>

install - the user wants the package installed or upgraded.

</li>
</ul>
<ul>
<li>

remove - the user wants the package removed, but does not want to remove any
existing configuration file.

</li>
</ul>
<ul>
<li>

purge - the user wants the package to be removed completely, including its
configuration files.

</li>
</ul>
<ul>
<li>

hold - the user wants this package not to be processed, i.e. wants to keep the
current version with the current status whatever that is.

</li>
</ul>

<hr>

<h2 id="s-puttingonhold">7.12 How do I put a package on hold?</h2>

There are three ways of holding back packages, with dpkg, apt or aptitude.

With dpkg, you have to export the list of package selections, with:

<pre>
 dpkg --get-selections \* &gt; selections.txt
</pre>

Then edit the resulting file <code>selections.txt</code>, change the line
containing the package you wish to hold, e.g. <code>libc6</code>, from this:

<pre>
 libc6 install
</pre>

to this:

Save the file, and reload it into dpkg database with:

<pre>
 dpkg --set-selections &lt; selections.txt
</pre>

With apt, you can set a package to hold using

<pre>
 apt-mark hold package_name
</pre>

and remove the hold with

<pre>
 apt-mark unhold package_name
</pre>

With aptitude, you can hold a package using

<pre>
 aptitude hold package_name
</pre>

and remove the hold with

<pre>
 aptitude unhold package_name
</pre>

<hr>

<h2 id="s-sourcepkgs">7.13 How do I install a source package?</h2>

Debian source packages can't actually be &quot;installed&quot;, they are just
unpacked in whatever directory you want to build the binary packages they
produce.

Source packages are distributed on most of the same mirrors where you can
obtain the binary packages. If you set up your APT's
<code>sources.list(5)</code> to include the appropriate &quot;deb-src&quot;
lines, you'll be able to easily download any source package by running

<pre>
 apt-get source foo
</pre>

To help you in actually building the source package, Debian source packages
provide the so-called build-dependencies mechanism. This means that the source
package maintainer keeps a list of other packages that are required to build
their package. To see how this is useful, run

<pre>
 apt-get build-dep foo
</pre>

before building the source.

<hr>

<h2 id="s-sourcebuild">7.14 How do I build binary packages from a source package?</h2>

The preferred way to do this is by using various wrapper tools. We'll show how
it's done using the <samp>devscripts</samp> tools. Install this package if you
haven't done so already.

Now, first get the source package:

<pre>
 apt-get source foo
</pre>

and change to the source tree:

Then install needed build-dependencies (if any):

<pre>
 sudo apt-get build-dep foo
</pre>

Then create a dedicated version of your own build (so that you won't get
confused later when Debian itself releases a new version):

<pre>
 dch -l local 'Blah blah blah'
</pre>

And finally build your package:

<pre>
 debuild -us -uc
</pre>

If everything worked out fine, you should now be able to install your package
by running

If you prefer to do things manually, and don't want to use
<samp>devscripts</samp>, follow this procedure:

You will need all of foo_*.dsc, foo_*.tar.gz and foo_*.diff.gz to compile the
source (note: there is no .diff.gz for some packages that are native to
Debian).

Once you have them (<a href="#s-sourcepkgs">How do I install a source package?,
Section 7.13</a>) and if you have the <code>dpkg-dev</code> package installed,
the following command:

<pre>
 dpkg-source -x foo_version-revision.dsc
</pre>

will extract the package into a directory called <samp>foo-version</samp>.

If you just want to compile the package, you may cd into the
<samp>foo-version</samp> directory and issue the command

<pre>
 dpkg-buildpackage -rfakeroot -b
</pre>

to build the package (note that this also requires the <code>fakeroot</code>
package), and then

<pre>
 dpkg -i ../foo_version-revision_arch.deb
</pre>

to install the newly-built package(s).

<hr>

<h2 id="s-creatingdebs">7.15 How do I create Debian packages myself?</h2>

For a more detailed description on this, read the New Maintainers' Guide,
available in the <code>maint-guide</code> package or at <code><a
href="http://www.debian.org/doc/devel-manuals#maint-guide">http://www.debian.org/doc/devel-manuals#maint-guide</a></code>,
or the Guide for Debian Maintainers, available in the <code>debmake-doc</code>
package or at <code><a
href="https://www.debian.org/doc/devel-manuals#debmake-doc">https://www.debian.org/doc/devel-manuals#debmake-doc</a></code>.

<hr>

The Debian GNU/Linux FAQ

<address>
version 9.0, 17 November 2018 
 
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a> 
 
</address>
<hr>

</body>

</html>

${this.title}

Code Editor : ch-pkg_basics.en.html