In this post I want to summarize the work done during my Outreachy internship with Debian project called “Bringing open-source mobile technologies to the new level with Debian (Osmocom)”. The main purpose of this project was to learn how to create packages in Debian (done), to create as many packages for Osmocom project (2 packages were more or less created) and, if possible, to improve documentation for building process (improvements were proposed).
During my internship I have found the packaging workflow and described it in my previous posts. …
In this post I want to provide some critique of Debian New Maintainers’ Guide, I want to show what could be enhanced and point out some places which were not clear for me.
First of all, I want to say that the overall quality of debian’s documentation is pretty good. It was hard to find mistakes because thousands people have read throughly the document and have already proposed some fixes and enhancements before me. But I was able to find flaws and I want to make my thoughts public.
From my point of view, the main limitation of the document is a lack of a general picture. The document is trying to teach us how to build the package by describing concrete steps and some exceptions. My own opinion is that in such documents the general picture must be provided in the very beginning. I agree that this is a hard task because having a lot of steps and exceptions you should find the most general ones which summarize the whole process. To illustrate my point of view, in the second chapter there is a description in 2.1 of a package building workflow. The first step is to get a copy of the upstream software. And in 2.2 there is a description of how to choose the program to package. But it’s a wrong order. Firstly, you have to find a good motivation for packaging and only after that you can choose the program to package. And even if you decide to package, it is not clear what documentation to read and in what order. So, from my point of view the document doesn’t provide a general picture of a packaging process. …
In this post I want to share my experience of package creation from scratch. I will show how to transform a program which consists of source code and some build system (e.g. autotools) to a deb package. Most probably this report won’t be full and will have some inaccuracies, so if you want to build a package in a proper way you should also read the official documentation.
Let’s summarize what should be done in order to create a debian package:
4. create patches for the package with…