Edit Generar paquetes debian sin usar debhelper

Title:

Last edited: 11:57:06 am on 2 February 2011 by salchicha

Esta explicación es una versión ligeramente modificada de la que ponen *aquí>http://ptspts.blogspot.com/2010/02/how-to-create-debianubuntu-package-deb.html*:

!How to create a Debian/Ubuntu package (.deb) manually

This blog post gives some hints how to create a .deb package file (to be used with Debian, Ubuntu and similar Linux distributions). The intended audience is programmers and system administrators, both with a strong Debian or Ubuntu Linux background and strong scripting skills. It is assumed that you know almost everything about your Linux system, you have installed .deb packages by hand (with dpkg. and apt-get), you understand the dependencies etc., and the only information you need how to create a .deb package from your software.

This blog post describes a low-level, hacky and quick approach with little automatic validation and instrumentation. This approach is useful for packages which don't require compilation or complicated runtime configuration. To start learning the more consistent, heavy-weight, validated approaches, fetch some source packages with apt-get source, and have a look at their debian subdirectories. The merit of our approach is simplicity (you have to understand only a few basic concepts to create your first package) and speed. Disadvantages are that it lets you create suboptimal, nonworking or nonstandard packages since there is only very little automatic validation, so you may sometimes recognize problems with your .deb packages too late, when it's too expensive to fix them; also this approach doesn't force you learn and follow the conventions and best practices of your Linux distribution.

First, have a look at the contents of .deb packages similar to your software. To get the <tt>.deb</tt> file, use <tt>apt-get -d install --reinstall ${PACKAGENAME}</tt>, and fetch the file you are interested in from /var/cache/apt/sources. Once you have the <tt>.deb</tt> file, extract it with <tt>dpkg-deb</tt>:

=$ dpkg-deb -x .../${MYFILE}.deb /tmp/${MYFILE}
=$ dpkg-deb -e .../${MYFILE}.deb /tmp/${MYFILE}/DEBIAN

Important text files are:

- <tt>/tmp/${MYFILE}/DEBIAN/control</tt>: all meta-information: package name, size, version number, dependencies, short description, long description 
- <tt>/tmp/${MYFILE}/DEBIAN/md5sums</tt>: md5sum values for all regular files in the package 
- <tt>/tmp/${MYFILE}/DEBIAN/postinst</tt>: executable script which will be run by dpkg -i after dependencies are installed, and files of this package are extracted 
- <tt>/tmp/${MYFILE}/DEBIAN/preinst</tt>: a similar executable script 
- <tt>/tmp/${MYFILE}/DEBIAN/prerm</tt>: another similar executable script 
- <tt>/tmp/${MYFILE}/DEBIAN/postrm</tt>: another similar executable script

Use Google to find out more about these (and possibly other) special files. To get examples, look at the special files of the packages installed to your system; those special files are in <tt>/var/lib/dpkg/info</tt>.

Google is your friend. Search for how to build a debian package. The first two results I've found seem to be useful, I strongly recommend you read them: *Debian-Binary-Package-Building-HOWTO>http://tldp.org/HOWTO/html_single/Debian-Binary-Package-Building-HOWTO/*; *How-to-make-deb-packages>http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/How-to-make-deb-packages/*. However, be prepared that some of the information you find is outdated or obsoleted. Always compare the instructions found on the web to what the packages of your distribution contain. Also be prepared that you don't find any definitive, comprehensive, up-to-date or useful documentation on a particular subtopic: learn from examples then.

Follow the these steps to create your <tt>.deb</tt> package:

# Learn everything you possible need to know, as indicated above. Learn primarily from examples (by examining some relevant packages on your Linux distribution). 
# Create a directory named <tt>${PACKAGENAME}_${VERSION}_${ARCHITECTURE}</tt>. We'll call this the package directory. 
# Create subdirectories and files in the package directory. For example, if you want to have your package contain <tt>/usr/bin/footool</tt>, then create <tt>usr</tt>, create <tt>usr/bin</tt> and copy your prebuilt <tt>footool</tt> binary to <tt>usr/bin</tt>. 
# Make sure the owner, group and permission bits are right (as intended on the target system) for all files and directories. 
# Create the <tt>DEBIAN</tt> subdirectory in the package directory. 
# Create your <tt>DEBIAN/control</tt> file, possibly copying a similar one, and modifying some fields. 
# If you need to run some code during installation after the package files are extracted to <tt>/</tt>, then create <tt>DEBIAN/postinst</tt> as a script (usually starting with <tt>#! /bin/sh</tt>), and make it executable. To prevent future troubles, make this script robust and idempotent, i.e. it should exit successfully even after a previous half-finished package installation. However, if there is something wrong in the system, the script should exit with a non-zero exit code. <tt>set -e</tt> can help here: it makes the shell running the script exit at the first nonsuccessful command (outside a subshell). 
# Compute md5sums by running <tt>md5sum `find . -type f | grep -v '^[.]/DEBIAN/'` >DEBIAN/md5sums<tt> in the package directory. 
# Set the <tt>Installed-Size:</tt> field of the <tt>DEBIAN/control</tt> file to last number in the total output of <tt>du -s</tt> run in the package directory. 
# Make sure that the package name, version number and architecture in the package directory name are the same is what's indicated in <tt>DEBIAN/control</tt>. 
# Make sure there are no backup files (<tt>&star;~</tt>, especially <tt>DEBIAN/&star;~</tt>) or temporary files lying around inside the package directory. 
# Go one level above the package directory, and run <tt>dpkg-deb -b ${PACKAGENAME}_${VERSION}_${ARCHITECTURE}</tt> . This creates <tt>${PACKAGENAME}_${VERSION}_${ARCHITECTURE}.deb</tt>. 
# Your <tt>.deb</tt> package is ready. Try installing it to your system (<tt>sudo dpkg -i ${PACKAGENAME}_${VERSION}_${ARCHITECTURE}.deb</tt>) . Play with it. Fix problems and rebuild it as many times as necessary. Increase the version number.

- lock this page
- enter new password
- reenter same password

Send e-mail alerts to these addresses upon next save: