Difference between revisions of "Development/Porting Packages"
From Maemo Leste Wiki
Jump to navigationJump to search (Add a placeholder that will be used to describe the procedure for forking a Debian/Devuan package) |
|||
| Line 22: | Line 22: | ||
If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard) | If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard) | ||
= Forking Debian/Devuan packages = | |||
(TODO - Describe what branches need to be set up, Jenkins integration, etc) | |||
Revision as of 03:12, 28 January 2020
Porting / Creating packages
If you're looking at creating your own package, or porting software, the first things to do are:
- Check if someone already ported the package (if it in the repository? Is there an issue for it?)
- Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
- (TODO)
Porting existing Maemo Fremantle packages
Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:
- Check if someone already ported the package (if it in the repository? Is there an issue for it?)
- Updating of the Debian packaging files/scripts.
- Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
- Fixing any compile errors/warnings due to more strict compile flags
Source of the packages can be found at one of these places:
If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)
Forking Debian/Devuan packages
(TODO - Describe what branches need to be set up, Jenkins integration, etc)
