Difference between revisions of "Packaging"
(Mention gbp.conf and add placeholders for Initial Packaging and Package Updating.) |
m (→Workflow) |
||
| Line 18: | Line 18: | ||
</pre> | </pre> | ||
This file is used by gbp, which in turn is used by | This file is used by gbp, which in turn is used by jenkins-debian-glue. | ||
The rest is standard Debian packaging. | The rest is standard Debian packaging. | ||
Revision as of 22:33, 13 April 2021
The packages we build for Maemo Leste are hosted on Github: https://github.com/maemo-leste
We use the Jenkins CI https://phoenix.maemo.org along with helper scripts that can be found at https://github.com/maemo-leste/jenkins-integration The base logic of buildng Debian packages in Jenkins comes from https://jenkins-debian-glue.org
Workflow
Our workflow consists of having the packages in Git, along with respective branches. The master branch in git should represent the latest development. When the sources are ready, we create a new branch called "maemo/ascii", which represents the Devuan suite we base it on.
Being git-based, our packages require the gbp.conf file inside the debian directory.
All of our packages contain the exact same gbp.conf, which is the following:
[DEFAULT] upstream-tag=%(version)s
This file is used by gbp, which in turn is used by jenkins-debian-glue.
The rest is standard Debian packaging.
Initial packaging
TODO
Updating a package
TODO
