English
Complete Guide to Building Software Packages on the Debian Platform
From maintainer scripts to hands-on packaging — a complete knowledge system for understanding Debian package building in one article.
Why is there this special topic?
When maintaining and delivering self-developed services, package the application into a standard .deb Packaging is the most standardized and easiest-to-maintain delivery method. However, Chinese-language materials on Debian packaging are either overly fragmented or remain at the "as long as it runs" level, lacking...Maintainer script lifecycle systematic explanation of.
This special topic was created precisely to solve this problem.
Special Topic Content Overview
This topic has a total of Six main articles+A reading guide, step by step build up a complete knowledge system of Debian packaging:
| Chapter | title | Core content |
|---|---|---|
| Introduction | This article | Special Topic Overview and Reading Guide |
| Prologue | Debian Packaging Primer | The troika of control, rules, and changelog |
| Chapter 1 | Complete interpretation of the postinst script | Post-install script execution mechanism and best practices |
| Chapter Two | Proper usage of the prerm script | Detailed scenario-based explanation of pre-uninstall scripts |
| Chapter 3 | Cleanup logic of the postrm script | The boundaries and pitfalls of remove vs purge |
| Chapter 4 | Golang Project Packaging in Practice | Multi-stage Docker build + systemd integration |
| Chapter 5 | Hands-on Vue Project Packaging | Static resource deployment + Nginx automatic configuration |
Who is this topic suitable for?
✅ Suitable for you if:
Need to package your own application (Go/Python/Node/VUE, etc.) as
.debPackage deliveryHope you understand.
postinst,prerm,postrmlifecycle and trigger scenariosWant to learn about production-grade packaging solutions, including systemd integration, configuration retention, data cleanup, etc.
We are setting up a CI/CD pipeline and need to standardize the build and delivery process.
⚠️ Not for you if:
Only want to use
fpmorcheckinstallBuild a "usable package", without caring about lifecycle conventions.No interest in Debian packaging at all (so how did you end up here? 😄)
Reading roadmap
Route 1: Systematic Learning (Recommended for Beginners)
Read from the prologue to chapter five in order to build a complete knowledge system.
Route 2: On-demand skimming (suitable for experienced developers)
| Your needs | Recommended Reading |
|---|---|
| I want to understand the lifecycle of maintainer scripts. | Chapter 1 → Chapter 2 → Chapter 3 |
| I want to package the Go project as a .deb. | Prologue → Chapter 4 |
| I want to package the VUE project as a .deb | Prologue → Chapter 5 |
encounter deconfigure Scene | Chapter 2 (focus on the deconfigure section) |
Encounter purge Cleanup issues | Chapter 3 (focus on the purge section) |
The core concept of the topic
1. Understand the lifecycle, rather than memorizing scripts
postinst,prerm,postrm do not exist in isolation; together they constitute the software package's full lifecycle Understanding when each script is triggered is more important than memorizing script templates.
2. Configuration preservation is the highest priority.
Never overwrite user-modified configuration files during upgrades. This is the first principle of Debian packaging. All scripts in this topic follow this principle.
3. Reproducible build environment
Use Docker multi-stage builds to ensure that anyone can build exactly the same result on any machine..deb Bag.
Practical Project Overview
This topic includes two complete practical case studies:
| Project Type | tech stack | packaged artifacts | Delivery format |
|---|---|---|---|
| Backend service | Golang + systemd | binary file | .deb bag |
| Frontend application | VUE + Nginx | Static resources + Nginx configuration | .deb bag |
Both cases include:
✅ Complete Docker build file (
builder.Dockerfile)✅ Automated build script (
Makefile)✅ Production-grade maintainer script (
postinst,prerm,postrm)✅ Deployment and Verification Guide
Usage recommendations
1. As a template reference
The scripts and configurations in this topic have all been verified in production environments and can serve as your project's Packaging template Copy and use directly. Just take appname/apiserver/cms-manager Simply replace it with your project name.
2. As learning material
If you are still unfamiliar with Debian packaging, it is recommended to start from the prologue and read in order. At the end of each chapter, there is also attached Practical Exercise and Pitfall Avoidance Guide, you can read and practice at the same time.
3. As a troubleshooting manual
If you encounter problems during actual packaging (for example postrm Failure causes the package to be unable to be reinstalled), you can jump directly to the corresponding section to view the problem analysis and solution.
Related resources
Official documentation
Community tools
| tool | Purpose | Applicable scenarios |
|---|---|---|
dh-make | Generate a Debian packaging template | Getting Started |
debhelper | Automated build toolset | Official recommended solution |
fpm | A simple and fast packaging tool | Rapid build, non-standard |
checkinstall | Generate .deb from source installation | personal use |
This topic adopts debhelper + dh + Docker Solution, balancing standardization and automatability.
Quick Start
If you want to Start immediately Package the Golang project as .deb, jump directly to:
👉Chapter 4: A Complete Guide to Packaging Golang Projects as Debian Packages
If you want to Start immediately Package the VUE project as .deb, jump directly to:
👉Chapter 5: Packaging a VUE Project as a Debian Package and Automatic Nginx Configuration
If you want to Learn from scratch, Please start from the prologue:
Keep updated
This series will be continuously revised based on updates to the Debian packaging toolchain and feedback from readers. If you have any suggestions, questions, or find a bug, you can contact me 🙌
Wish you a happy packing!🚀
