GNU/Linux Desktop Survival Guide by Graham Williams
Desktop Survival Project Home Preface Advocacy History Distributions Installing GNU/Linux Basic Survival Wajig Applications AI, Machine Learning, Data Science Android - GNU/Linux Devices Audio Backup Booting CD Chinese ChRoot Clock Cloud Computing Command Line Databases DIA Directories Disks Emacs EcoSysL Email Evolution Files File Systems Firewalls Floppy Disks FreedomBox Fonts Ghemical Glade GNOME Graphics, Images, Photos Hardware Initialisations on Booting Installation Examples IOT Java KDE Kernels Keyboard Konqueror KVM Switch LaTeX Log System Login Magellan MATE Mathematics Memory Modems Mounting Devices MS/Windows Music MySQL Nautilus Networks NFS NT File System Oracle Packages Partitions Passwords PDF Power Management PPP Presentations Printing Python R Remote Desktops Rsync Samba Scanning Science Screens Security Sketch Spell SPlus Spruce Spreadsheet SSH SUDO Swap Teradata Data Warehouse Themes TV Unity USB Version Control Video Virtualization Voice over IP World Wide Web WebCam WordPress Web Sites Word Processing and Printing X XML Troubleshooting Index

CLICK HERE TO VISIT THE UPDATED SURVIVAL GUIDE

Packages: Debian Style

Debian Packages: doc-debian debian-policy debmake devscripts fakeroot apt dpkg make g++ gcc perl autoconf sed libc6-dev

You can become part of the international effort that is Debian GNU/Linux by maintaining finding a package that you use regularly but is not available under Debian. You can then package it up and perhaps even become a Debian developer yourself. The steps to take include:

1. Read the developer documentation at http://www.debian.org/doc/devel-manuals, probably starting with the "New Maintainer's Guide" at http://www.debian.org/doc/maint-guide/. Most of these manuals can be installed as debian packages and read offline.
2. Send a message to the debian-devel mailing list with a subject line ITP: mynewpackage (the ITP stands for Intend to Package). This will let others know your intention, and serve to double check that it has not already been done, and that it is worth doing!
3. Find a Debian developer that will sponsor you.
4. Your sponsor will have access to the debian machines and can test your package on all the architectures with you.

We will use as an example the packaging of a Debian tool called wajig. It is a simplified front end to the APT and DPKG suite of tools. It is a python program. We use autoconf to manage the configuration and turned the tool into a Debian package using the steps outlined below. We essentially follow the example in the Debian Policy Manual at http://www.debian.org/doc/debian-policy/.