Development/Building Packages - Revision history

Arno11-n900: /* Maemo Leste Extras */

2026-09-19T15:14:19Z

Maemo Leste Extras

← Older revision		Revision as of 15:14, 19 September 2026
Line 98:		Line 98:
	= Maemo Leste Extras =		= Maemo Leste Extras =

	If you wish to maintain your own package in Maemo Leste, you can apply a package at https://~~github~~.~~com~~/~~maemo-~~leste-extras/bugtracker		If you wish to maintain your own package in Maemo Leste, you can apply a package at https://git.maemo.org/leste-extras/bugtracker
	Have a look at the README in that repository and open a ticket.		Have a look at the README in that repository and open a ticket.

Arno11-n900: /* How packages are built using Jenkins */

2026-09-19T15:13:02Z

How packages are built using Jenkins

← Older revision		Revision as of 15:13, 19 September 2026
Line 85:		Line 85:
	Read only access to the http frontend: https://phoenix.maemo.org/ (write-access can be granted)		Read only access to the http frontend: https://phoenix.maemo.org/ (write-access can be granted)

	All packages are hosted on https://~~github~~.~~com~~/~~maemo-leste~~ and a current list of all the packages in Jenkins can be found here:		All packages are hosted on https://git.maemo.org/explore/repos and a current list of all the packages in Jenkins can be found here:

	https://~~github~~.~~com~~/~~maemo-~~leste/jenkins-integration/~~blob~~/master/config.py		https://git.maemo.org/leste/jenkins-integration/src/branch/master/config.py

	Every repository has a branch for each release, for example:		Every repository has a branch for each release, for example:

Arno11-n900: /* Submitting changes */

2026-09-19T15:10:21Z

Submitting changes

← Older revision		Revision as of 15:10, 19 September 2026
Line 57:		Line 57:
	== Submitting changes ==		== Submitting changes ==

	If you make changes to a package, please submit a pull request for the repository of that package, likely: https://~~github~~.~~com~~/~~maemo~~-~~leste~~/PACKAGENAME		If you make changes to a package, please submit a pull request for the repository of that package, likely: https://git.maemo.org/leste-extras/PACKAGENAME

	For now, we will take care of updating tags and branches.		For now, we will take care of updating tags and branches.

Arno11-n900: /* Maintenance workflow */

2026-09-19T15:09:25Z

Maintenance workflow

← Older revision		Revision as of 15:09, 19 September 2026
Line 3:		Line 3:
	Each package in Maemo Leste uses a specific git-based workflow which makes it easy to track history and maintain in an easy way.		Each package in Maemo Leste uses a specific git-based workflow which makes it easy to track history and maintain in an easy way.

	Taking the https://~~github~~.~~com~~/~~maemo-~~leste/libcal/ package as an example - a valid repository contains at least two git branches:		Taking the https://git.maemo.org/leste/libcal package as an example - a valid repository contains at least two git branches:

	# master		# master

Sicelo: /* The git tag */

2021-04-14T16:14:23Z

The git tag

← Older revision		Revision as of 16:14, 14 April 2021
Line 28:		Line 28:
	Once tagged, push the tag to git origin.		Once tagged, push the tag to git origin.

	NB: The tags are used to checkout the source code itself, the debian directory is always taken from git HEAD		NB: The tags are used to checkout the source code itself, the debian directory is always taken from git HEAD, so there is no need to update the tag when changing the packaging (i.e. in debian directory). Tag shall be updated only when there are changes to the source files.

	== gbp.conf ==		== gbp.conf ==

Sicelo: /* The git tag */

2021-04-14T16:02:25Z

The git tag

← Older revision		Revision as of 16:02, 14 April 2021
Line 27:		Line 27:

	Once tagged, push the tag to git origin.		Once tagged, push the tag to git origin.

			NB: The tags are used to checkout the source code itself, the debian directory is always taken from git HEAD

	== gbp.conf ==		== gbp.conf ==

Parazyd: /* Adding an icon to the package in HAM */

2020-11-02T11:55:41Z

Adding an icon to the package in HAM

← Older revision		Revision as of 11:55, 2 November 2020
Line 109:		Line 109:
	In case you want to add an icon that is shown in HAM when listing the packages, we provide a debhelper plugin that can		In case you want to add an icon that is shown in HAM when listing the packages, we provide a debhelper plugin that can
	handle this with a simple PNG file. In your package's debian directory, add your PNG icon as '''maemo-icon.png'''.		handle this with a simple PNG file. In your package's debian directory, add your PNG icon as '''maemo-icon.png'''.
	Next, have your Build-Depends contain '''maemo-system-services'''. maemo-system-services will pull in the debhelper plugin.		Next, have your Build-Depends contain '''maemo-system-services-dev'''. maemo-system-services-dev will pull in the debhelper plugin.
	Following this, in your '''debian/control''', under your '''Package''', add the following entry:		Following this, in your '''debian/control''', under your '''Package''', add the following entry:

Parazyd: /* Maemo Leste Extras */

2020-11-02T11:54:07Z

Maemo Leste Extras

← Older revision		Revision as of 11:54, 2 November 2020
Line 123:		Line 123:
	dh_gencontrol		dh_gencontrol
	</pre>		</pre>

			Finally, if using quilt, add the icon in '''debian/source/include-binaries'''

			<pre>$ echo debian/maemo-icon.png >> debian/source/include-binaries</pre>

			Further reading: https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections

Parazyd: /* Maemo Leste Extras */ Note dh_maemo_icon

2020-11-02T10:40:04Z

Maemo Leste Extras: Note dh_maemo_icon

← Older revision		Revision as of 10:40, 2 November 2020
Line 104:		Line 104:
	<code>debian/control</code> file has a correct <code>section</code> clause as explained on the [https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections\|Maemo Packaging Wiki]. This wiki page also explains how to have HAM show your application's icon. Note that having an icon showing in HAM is a separate issue from having an icon show up in the application list (Hildon Home). The latter is done through		<code>debian/control</code> file has a correct <code>section</code> clause as explained on the [https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections\|Maemo Packaging Wiki]. This wiki page also explains how to have HAM show your application's icon. Note that having an icon showing in HAM is a separate issue from having an icon show up in the application list (Hildon Home). The latter is done through
	<code>.desktop</code> files, while the former is done in <code>debian/control</code>.		<code>.desktop</code> files, while the former is done in <code>debian/control</code>.

			== Adding an icon to the package in HAM ==

			In case you want to add an icon that is shown in HAM when listing the packages, we provide a debhelper plugin that can
			handle this with a simple PNG file. In your package's debian directory, add your PNG icon as '''maemo-icon.png'''.
			Next, have your Build-Depends contain '''maemo-system-services'''. maemo-system-services will pull in the debhelper plugin.
			Following this, in your '''debian/control''', under your '''Package''', add the following entry:

			<pre>
			XB-Maemo-Icon-26: ${maemo:icon26}
			</pre>

			And finally, in '''debian/rules''', assuming you're using debhelper, add this:

			<pre>
			override_dh_gencontrol:
			dh_maemo_icon
			dh_gencontrol
			</pre>

Parazyd: Ascii to Beowulf

2020-09-30T08:23:41Z

Ascii to Beowulf

← Older revision		Revision as of 08:23, 30 September 2020
Line 6:		Line 6:

	# master		# master
	# maemo/~~ascii~~		# maemo/beowulf

	Ideally, the branches should have no difference, but sometimes this may vary.		Ideally, the branches should have no difference, but sometimes this may vary.
Line 71:		Line 71:

	<code>		<code>
	deb https://maedevu.maemo.org/leste ~~ascii~~ main contrib non-free		deb https://maedevu.maemo.org/leste beowulf main contrib non-free

	deb https://maedevu.maemo.org/extras ~~ascii~~ main contrib non-free		deb https://maedevu.maemo.org/extras beowulf main contrib non-free
	</code>		</code>

	Packages in this repository get build by Jenkins, to which a select group of people has access. (Parazyd, Wizzup~~, Spinal84~~)		Packages in this repository get build by Jenkins, to which a select group of people has access. (Parazyd, Wizzup)


Line 89:		Line 89:
	Every repository has a branch for each release, for example:		Every repository has a branch for each release, for example:

	# maemo/~~ascii~~ - main branch for Devuan ~~Ascii~~ target		# maemo/beowulf - main branch for Devuan Beowulf target
	# maemo/~~ascii~~-devel - optional branch for Devuan ~~Ascii~~ with unstable/testing version		# maemo/beowulf-devel - optional branch for Devuan Beowulf with unstable/testing version
	~~# maemo/beowulf - main branch for Devuan Beowulf version of the package~~

	See [[Development/Branches]] for more information on the usual branches flow.		See [[Development/Branches]] for more information on the usual branches flow.