I can recommend using one of Debian's tools to create the first package skeleton.
dh-make for single packages or libs
dh-make-perl for perl packages
dh-make-php . . .
Takes care of most of the boilerplate
dh_make example export DEBFULLNAME=”Hack Er” dh_make –email [email_address] --copyright=bsd --file ../foo.tar.gz This is all you really need to get started in most cases. Note that you should be in the source directory to run this.
What do we end up with? $ tar xvf pyyaml_3.05.orig.tar.gz $ ls examples ext lib LICENSE PKG-INFO README setup.cfg setup.py setup_with_libyaml.py $ mv PyYAML-3.05 pyyaml-3.05 $ ls debian examples ext lib LICENSE PKG-INFO README setup.cfg setup.py setup_with_libyaml.py Oh! A debian dir!
“ The important part to know about the rules file created by dh_make, is that it is just a suggestion. It will work for simple packages but for more complicated ones, don't be afraid to add and subtract from it to fit your needs. Only thing that you must not change are the names of the rules, because all the tools use these names, as mandated by the Policy.”
“ A collection of programs that can be used in a debian/rules file to automate common tasks related to building debian packages. Programs are included to install various files into your package, compress files, fix file permissions, integrate your package with the debian menu system, debconf, doc-base, etc. Most debian packages use debhelper as part of their build process.”
Yeah, there is apt-get and .debs, but don't be fooled, maemo is not debian
This means that maemo does not have to follow debian's conventions, it is free to innovate without having to go through the traditional debian decision making process – which debian's founder calls “Process run amok.”