Remove Debian parts as these are still in WIP

builders/README.md

@@ -4,15 +4,11 @@ CI / Nightly-Builders
 ## About
 
 Scripts and Dockerfiles for Geany and Geany-Plugins nightly builds.
-`start_build.sh` will create (if missing) Docker images for
-Debian stable and unstable as well as a Docker image for Mingw-w64
-cross-compilaton to Windows.
-For the created Debian packages repositories for the distributions
-(stable and unstable) will be created.
+`start_build.sh` will create (if missing) a Docker image for
+Mingw-w64 cross-compilaton to Windows.
 
 ## Scripts and files
 
-    ├── Dockerfile.debian                   -> Dockerfile for Debian build image
     ├── Dockerfile.mingw64                  -> Dockerfile for Mingw-64 build image
     ├── README.md
     ├── certificates                        -> Certificate for signing Windows binaries and installer
@@ -29,12 +25,7 @@ For the created Debian packages repositories for the distributions
     │           └── mirrorlist.mingw64
     ├── output                              -> Directory where all build results are stored
     │
-    ├── scripts                             -> Build scripts to be executed within Docker containers
-    │   ├── build_debian_geany.sh           -> Build Geany Debian packages
-    │   ├── build_debian_geany_plugins.sh   -> Build Geany-Plugins Debian packages
-    │   └── update_debian_repositories.sh   -> Build repositories for Debian packages
-    │
-    └── start_build.sh                      -> Run Debian and Windows build containers and start builds
+    └── start_build.sh                      -> Run Windows build containers and start builds
 
 ## Geany sources
 
@@ -49,10 +40,7 @@ Geany resp. Geany-Plugins from GIT master.
 Main entry point to (re-)build the necessary Docker images and trigger
 the builds of Geany and Geany-Plugins for the various targets.
 
-    usage: start_build.sh [-d|--distro DISTRO] [-m|--mingw64]
-                          [-r|--rebuild-images]
-     -d, --distro DISTRO     Build for target Debian DISTRO (e.g. "bullseye",
-                             can be specified multiple times
+    usage: start_build.sh [-m|--mingw64] [-r|--rebuild-images]
      -f, --force-rebuild     Force rebuilding of immages even if not necessary
      -g, --geany             Build Geany
     --geany-script           Path to the script to be executed to build Geany
@@ -68,35 +56,9 @@ the builds of Geany and Geany-Plugins for the various targets.
      -s, --sudo              Use "sudo" for Docker commands
 
 
-Example to build Geany and Geany-Plugins for Debian Bullseye, Debian Sid and Windows:
-
-    bash start_build.sh --geany --geany-plugins --mingw64 --distro sid --distro bullseye
-
-## Debian package build
-
-The Debian based builds use as much as possible the official Debian package sources
-from https://salsa.debian.org/geany-team/geany.git (and resp. for Geany-Plugins).
-
-Within the Debian based Docker images, packages are built from a GIT clone of Geany (unless
-a source tree is provided into the container via a volume).
-
-### Docker image
-
-The Debian based Docker image is pretty straight-forward and just extends the official
-"debian:$distro" images. The base image can be passed as build argument on image building and
-so images for different Debian distributions (stable, sid, ...) can be built for later use.
-
-The Dockerfile just installs a couple of development tools and libraries which are required for
-building Geany and Geany-Plugins. This is mainly to prepopulate the image with commonly used
-tools and libraries.
-
-### Repository creation
-
-TBW - WIP
-
-#### GnuPG key
+Example to build Geany and Geany-Plugins for Windows:
 
-TBW - WIP
+    bash start_build.sh --geany --geany-plugins --mingw64
 
 ## Windows (Mingw64) build