From 9cca281cd663f1e463053d1ae95605b6a490f749 Mon Sep 17 00:00:00 2001 From: ConnoratLeft Date: Wed, 19 Jun 2019 10:26:49 -0700 Subject: [PATCH] Update README.md --- tutorial-2/README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/tutorial-2/README.md b/tutorial-2/README.md index 7793434..cc8d0d4 100644 --- a/tutorial-2/README.md +++ b/tutorial-2/README.md @@ -48,8 +48,8 @@ dpkg-buildpackage requires you to specify: These specifications are stored in text files inside a directory named `debian`. This directory is expected to live inside the application's source directory. So the structure you end up with looks as follows: - hello - ...and other application source files... + + ...application source files... debian/ control changelog @@ -59,17 +59,17 @@ These specifications are stored in text files inside a directory named `debian`. Then you invoke dpkg-buildpackage (`dpkg-buildpackage -b`) from the application's source directory. Dpkg-buildpackage compiles the application using your instructions. It also creates the package root directory (under `debian/`) and create files in there based on your instructions on how that should be done. At this point you end up with a structure like so: - hello - ...and other application source files... + ...application source files... debian/ control changelog compat rules + copyright ...and other specification files... - hello/ <--- this is the package root - DEBIAN/ + package_name/ <--- this is the package root which will be moved to your machines root upon installation + DEBIAN/ <--- This folder isn't in the package after installing the deb control ...and other metadata files... usr/