Differences between revisions 2 and 3
Revision 2 as of 2006-04-10 10:48:52
Size: 2438
Editor: EddyPetrisor
Comment: First step of package creation
Revision 3 as of 2006-04-10 10:49:32
Size: 2440
Editor: EddyPetrisor
Comment: spelling
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
''If the nformation below seem scarce, please look in the [http://www.debian.org/doc/maint-guide/ New Maintainer's Guide] and in the [http://www.debian.org/doc/debian-policy/ Debian Policy].'' ''If the information below seems scarce, please look in the [http://www.debian.org/doc/maint-guide/ New Maintainer's Guide] and in the [http://www.debian.org/doc/debian-policy/ Debian Policy].''

Introduction

This page is intended to gather a pragmatic guide ?HowTo guide into creating a Debian package.

Why does this page even exist?

Since the [http://www.debian.org/doc/debian-policy/ Debian Policy] and [http://www.debian.org/doc/manuals/maint-guide/index.en.html the Debian New Maintainers' Guide] sometimes are too big to read for the people that prefer a more pragmatic approach to problems, this howto will focus on a pargmatic approach on learning to create Debian packages.

Creating the package

If the information below seems scarce, please look in the [http://www.debian.org/doc/maint-guide/ New Maintainer's Guide] and in the [http://www.debian.org/doc/debian-policy/ Debian Policy].

If you want to create an official package make sure is not already packaged. If [http://www.us.debian.org/devel/wnpp/being_packaged somebody is working on the package] , then you should contact she/he if you intent to make an official package together. More info in the [http://www.debian.org/doc/maint-guide/ New Maintainer's Guide].

Initial compilation

Steps:

  • try compile the package (do not run install) - can be done on your system, but is preferably done in a chroot
    • write down every package you had to install so the package compiled (will be added to build dependency)
    • write down quirks and tricks needed for the package to compile (files missing, file modifications, etc.)

If the package compiles then it means you might have figured out all the dependencies; don't worry, this will be checked later in a chroot environment.

DO NOT run make install, unless you are absolutely sure. Broken installation scripts are very much present unfortunetely and you don't want yet to run a test installation.

Debianization

TODO: add notes

Initial compilation of the package

TODO: add notes

All tests in chroot

  • Why is a good idea to use a chroot

TODO: add notes

Testing the package

TODO: add notes

Linda

TODO: add notes

Lintian

TODO: add notes

Piuparts

TODO: add notes

This page is still incomplete; please help completing it by adding information to it. Do not forget that the information here should be in a concise form.

Notes: [20060410] EddyPetrisor is working on this; an initial complete page should be ready in a week, at most.