Revision as of 23:03, 16 December 2020

This page describes some basics in taking a package from https://invent.kde.org/neon/ and building it locally. This can be useful for doing local testing before committing changes.

Prerequisites

A pre-existing KDE development environment
dpkg-dev package will include the standard debian toolchain for building packages.

Setting up local files for building package

Clone the package repository repository, i.e. https://invent.kde.org/neon/kde/libkdegames
Copy the source tree from your kde sources to where the debian/ path resides.
Create a usr/share/locale to simulate CI locale injection, mkdir -p usr/share/locale && touch usr/share/locale/stub
Remove symbols to simulate CI removing the symbol files, rm debian/*.symbols

Building the package

Because a tarball does not exist, you will need to tell the package builder to not clean the environment before build -nc. It's helpful to further clean the environment after -tc for easier git usage for committing content. To do this, run:

dpkg-buildpackage -nc -tc

Alternatively, change the contents of debian/source/format to native and the tooling can be used without specifying options like -nc.

@@ Line 14: / Line 14: @@
 = Building the package =
-Because a tarball does not exist, you will need to tell the package builder to not clean the environment before build <code>-nc</code>. It's helpful to further clean the environment after for easier git usage for committing content To do this, run:
+Because a tarball does not exist, you will need to tell the package builder to not clean the environment before build <code>-nc</code>. It's helpful to further clean the environment after <code>-tc</code> for easier git usage for committing content. To do this, run:
 <code>dpkg-buildpackage -nc -tc</code>
-Alternatively, modify <code>debian/source/format</code> with <code>native</code> and the tooling can be used without specifying options like <code>-nc</code>.
+Alternatively, change the contents of <code>debian/source/format</code> to <code>native</code> and the tooling can be used without specifying options like <code>-nc</code>.