Difference between revisions of "Packaging"
(Initial commit) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
The packages we build for Maemo Leste are hosted on Github: https://github.com/maemo-leste | 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 | 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 = | = Workflow = | ||
| Line 7: | Line 8: | ||
Our workflow consists of having the packages in Git, along with respective branches. | 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. | 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: | |||
<pre> | |||
[DEFAULT] | |||
upstream-tag=%(version)s | |||
</pre> | |||
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 | |||
= Links = | |||
* https://wiki.maemo.org/Packaging | |||
* https://wiki.maemo.org/Extras-testing/Command_line_applications | |||
* https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Application_Development/Writing_a_new_maemo_application#Adding_application_to_menu | |||
Latest revision as of 23:33, 9 October 2022
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
