Delve into the Debian package ecosystem, learn about repositories, package tools, and build packages using the fpm tool, enhancing your deployment skills and integration efficiency.

docker15.tar.gz

buildingPackage1-UsingBuildSystem-copy

buildingPackage2-Makefile-copy

buildingPackage3-custombuild-copy

buildingPackage4-installFile-copy

Exercise-buildingPackage-copy

Exercise1-solution-buildingPackage-copy

buildingPackage5-multi-package-dhmoves-copy

buildingPackage6-multi-package-dhinstall-copy

Exercise-buildingPackage-multipackage-copy

Exercise2-solution-buildingMultiplePackage-dhinstall-copy

Exercise3-solution-buildingMultiplePackage-copy

aptly-RemoveAtEnd

aptly-copy

Exercise-aptly-endpoints

Exercise_aptly-nginx

Packages are fundamental units of software deployment in Debian and related operating systems. Packaging enables users to deploy your packages using the built-in tools of their operating system.

In this course, you’ll learn about the environment that Debian packages live in, including repositories, package management installation tools, source and binary packages, and the “upstream” concept. Then you’ll learn about the structure and metadata of packages and an efficient way to build Debian packages using the fpm tool. You’ll also learn to use the Debian Build System, including the tools used to create package skeletons and multiple packages from a single code base. You’ll finish with an introduction to repository and package management and integrity.

By the end of this course, you’ll have learned about the Debian package ecosystem and several ways to build and package. This will enable you to seamlessly integrate your packages into existing infrastructure and take your deployment skills to the next level.

Building Debian Packages from the Ground Up

# Adding special files

There are some files that we simply place into our `debian/`
directory and that various debhelpers automatically pick up and install
for us:

* `preinst` or `<package-name>.preinst` is run before package
  installation.
* `postinst` or `<package-name>.postinst` is run after package
  installation.
* `prerm` or `<package-name>.prerm` is run before package removal.
* `postrm` or `<package-name>.postrm` is run after package removal.
* `init` or `<package-name>.init` is used as an init script for our
  package (though it has largely been replaced by `systemd`).
* `copyright` is supposed to be a machine-readable description of
  copyright and
  licenses
  that is installed to `/usr/share/doc/<package-name>/copyright`.

> **Note:** In all of these cases, the `<package-name>.<suffix>` form is usually
recommended and required for multi-package builds.

Some of the debhelper scripts assume that the (pre, post) (inst, rm)
scripts are shell scripts and inject their own code into them. To
enable that, we must include the special marker `#DEBHELPER#` as a line
on its own in these scripts.

Learn how to add special files to the Debian package.

Permissions and Fakeroot

Adding Special Files

Introduction

Debian Packages in Context

What's Inside a Debian Package

Quick Package Construction with fpm

The Debian Build System

Quick Debian Packaging and Multipackage Builds

Repository Management

Conclusion

Appendix

Adding Special Files

Adding special files