Differences

This shows you the differences between two versions of the page.

--- start [2024/02/18 15:51] – [Example: building openarc package from experimental] abeverley
+++ start [2024/09/04 08:23] (current) – abeverley
@@ Line 33: / Line 33: @@
   apt-get source openarc
   cd openarc-1.0.0~beta3+dfsg/
+  # Download additional patches
   cd debian/patches
   wget https://github.com/trusteddomainproject/OpenARC/pull/167.patch
   wget https://github.com/trusteddomainproject/OpenARC/pull/168.patch
   wget https://github.com/trusteddomainproject/OpenARC/pull/170.patch
+  wget https://github.com/trusteddomainproject/OpenARC/pull/173.patch
+  # Apply
+  cd ../..
+  patch -p1 < debian/patches/167.patch
+  patch -p1 < debian/patches/168.patch
+  patch -p1 < debian/patches/170.patch
+  patch -p1 < debian/patches/173.patch
   dch --bpo # Add letter to suggested version
+  dpkg-source --commit
   debuild -uc -us
@@ Line 46: / Line 55: @@
 Versioning info: https://www.debian.org/doc/debian-policy/ch-controlfields.html#version
+===== Building Debian packages of Perl modules =====
+On production servers, I much prefer to use Perl modules from Debian repositories, rather than installing from CPAN or using some sort of pinning technique. The advantage is that they are maintained upstream, are more stable, faster to install and easier overall to manage.
+Sometimes a Perl module is either not available in the main Debian repositories, or the version is too old (or I need a patch that has not made it upstream yet). In these circumstances I build my own Debian packages of Perl modules. Normally building a package is easy, but sometimes it can be a bit of an art. Read more about [[building Debian packages of Perl modules]].
 ===== JSON Web Tokens with Perl =====