From 27d3313807296c3943a96ceef8c2b7279cb56962 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Sat, 18 May 2024 19:39:59 +0200
Subject: Adding debian version 6.7.7-1.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 debian/README.source | 40 ++++++++++++++++++++--------------------
 1 file changed, 20 insertions(+), 20 deletions(-)

(limited to 'debian/README.source')

diff --git a/debian/README.source b/debian/README.source
index f6c57bf5b7..3dd01d12c0 100644
--- a/debian/README.source
+++ b/debian/README.source
@@ -114,30 +114,30 @@ number of files under debian/config and (if it exists)
 debian/config.local.  They are read in the following order, such that
 files later on the list can override settings from earlier files.
 Files in debian/config.local can also override settings from the
-corresponding file in debian/config.  Most of the files are optional
-and the filenames can generally be overridden by explicit lists
-(possibly empty) specified in the 'defines' files.
+corresponding file in debian/config.
 
 1. Common:
    - Default filename: config
-   - Filename list: [image]configs in defines
+   - Filename list: [build.config]
 2. Per kernel architecture:
-   - Filename: kernelarch-<karch>/config (optional)
-3. Per architecture:
+   - Default filename: kernelarch-<karch>/config
+   - Filename list: [kernelarch.build.config]
+3. Per Debian architecture:
    - Default filename: <arch>/config
-   - Filename list: [image]configs in <arch>/defines
-4. Per architecture and flavour:
-   - Default filename: <arch>/config.<flavour> (optional)
-   - Filename list: [<flavour>_image]configs in <arch>/defines
+   - Filename list: [kernelarch.debianarch.build.config]
+4. Per Debian architecture and flavour:
+   - Default filename: <arch>/config.<flavour>
+   - Filename list: [kernelarch.debianarch.flavour.build.config]
 5. Per featureset:
-   - Default filename: featureset-<fset>/config (optional)
-   - Filename list: [image]configs in featureset-<fset>/defines
-6. Per architecture and featureset:
-   - Default filename: <arch>/<fset>/config (optional)
-   - Filename list: [image]configs in <arch>/<fset>/defines
-7. Per architecture, featureset, and flavour:
-   - Default filename: <arch>/<fset>/config.<flavour> (optional)
-   - Filename list: [<flavour>_image]configs in <arch>/<fset>/defines
+   - Default filename: featureset-<fset>/config
+   - Filename list: [featureset.build.config]
+6. Per Debian architecture and featureset:
+   - Default filename: <arch>/<fset>/config
+   - Filename list: [kernelarch.debianarch.featureset.build.config]
+7. Per Debian architecture, featureset, and flavour:
+   - Default filename: <arch>/<fset>/config.<flavour>
+   - Filename list:
+     [kernelarch.debianarch.featureset.flavour.build.config]
 
 You can check the final list of configuration files by reading
 debian/rules.gen.  Each binary-arch_<arch>_<fset>_<flavour>_image
@@ -159,7 +159,7 @@ The master control file debian/control must be generated before
 the package is uploaded. debian/rules contains the debian/control 
 target, which generates the control file by invoking the 
 debian/bin/gencontrol.py script, which combines the templates from
-the templates directory and architecture-specific defines file to
+the templates directory and architecture-specific defines.toml file to
 produce the debian/control file. Note that this target is intentionally
 made to fail with a non-zero exit code to make sure that it is never
 run during an automatic build. The following variables are substituted
@@ -179,7 +179,7 @@ into the templates:
                -image descriptions.
 
 Normally, the arch-specific contents should be controlled by
-adjusting the corresponding defines file.
+adjusting the corresponding defines.toml file.
 
 Build-dependencies that relate to specific binary packages can be
 specified in a Build-Depends field in the template for that binary
-- 
cgit v1.2.3