From d041fa3bfc44344a3847667a8a3aa814a9fc5b7c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maxime=20=E2=80=9Cpep=E2=80=9D=20Buquet?= Date: Tue, 7 Aug 2018 13:16:43 +0100 Subject: [PATCH] WIP MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Maxime “pep” Buquet --- content/posts/debian-package-source.md | 28 ++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 content/posts/debian-package-source.md diff --git a/content/posts/debian-package-source.md b/content/posts/debian-package-source.md new file mode 100644 index 0000000..bd97bce --- /dev/null +++ b/content/posts/debian-package-source.md @@ -0,0 +1,28 @@ +--- +title: "Debian Package Sources" +date: 2018-07-18T15:26:20+01:00 +draft: true +--- + +_Disclaimer: I am an ArchLinux user, pretty accustomed to the ways of +`PKGBUILD`s and `makepkg` packaging-wise. I think that Debian packaging is +full of historical decisions that make it bloated, and hard to use in many +ways, and that there is too many things to rant about that I could ever have +time for. Unfortunately I don't have much experience with other packaging +systems._ + +_I hope to write more about other pain points of the Debian packaging system, +(as well as Arch's), in the future._ + +After this free taunt, let's get to the point. + +- Why am I not able to define the format of the source of truth myself. + +> The source archive scheme described later is intended to allow a Debian +> package source tree with some associated control information to be +> reproduced and transported easily. The Debian package source tree is a +> version of the original program with certain files added for the benefit of +> the packaging process, and with any other changes required made to the rest +> of the source code and installation scripts. +> The extra files created for Debian are in the subdirectory `debian` of the +> top level of the Debian package source tree. They are described below.