From df34fad0cfddc43182c56eaae1c0d0f1cb2e1d18 Mon Sep 17 00:00:00 2001 From: q-posev Date: Wed, 16 Feb 2022 18:16:19 +0100 Subject: [PATCH] Update README --- debian/README.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/debian/README.md b/debian/README.md index 6b1f840..69f1bf8 100644 --- a/debian/README.md +++ b/debian/README.md @@ -13,7 +13,7 @@ Following the [debian guide](https://www.debian.org/doc/manuals/debmake-doc/ch08 ## First release 1. Download and extract the Autotools-produced distribution tarball (e.g. `trexio-2.1.0.tar.gz`) -2. `mv trexio-2.1.0.tar.gz libtrexio_2.1.0.orig.tar.gz` --> important for step 4 +2. `cp trexio-2.1.0.tar.gz libtrexio_2.1.0.orig.tar.gz` --> important for step 4 3. `cd trexio-2.1.0` 4. `debmake` @@ -26,3 +26,14 @@ This relies on the previously created and modified templates in the `debian` dir 1. `debuild` --> this creates the debian packages in the parent directory, i.e. one level higher than `trexio-2.1.0/` directory 2. `dpkg -f libtrexio_2.1.0-1_amd64.deb pre-depends depends recommends conflicts break` + +**Note for maintainers:** to battle-test your build process, it can be a good idea to run `debuild` in a `chroot` environment +as opposed to the host. For example, `pbuilder` can be used to create an isolated `chroot` +and to build a debian package within it (see `pdebuild` wrapper command). + +## Make + +TREXIO supplies `make debian_from_dist` rule to produce a `libtrexio` debian package. +It relies on specifications in the `debian/` folder. +This rule should be executed in the source code distribution (extracted from the tarball) and **not in the GitHub repo clone**. +It also requires the tarball distribution (e.g. `trexio-2.1.0.tar.gz`) to be present in the **parent** directory.