From 05ef32d0ae12fff881c678743db271b747ca7d7b Mon Sep 17 00:00:00 2001 From: deep-42-thought Date: Wed, 15 Feb 2017 10:08:46 +0100 Subject: style only --- Build-system.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Build-system.md b/Build-system.md index 09a99c3..9030eda 100644 --- a/Build-system.md +++ b/Build-system.md @@ -21,7 +21,7 @@ The build system will consist from the following shell scripts: - arch32build: build packages in a clean chroot (a fork of [archbuild](https://git.archlinux.org/devtools.git/tree/archbuild.in)) - db-update: add binary packages to the repository, and remove them from the build list (a fork of [db-update](https://git.archlinux.org/dbscripts.git/tree/db-update)) -## get-package-updates +### get-package-updates 1. Create a lock file for build list. 2. Update git repositories ([official packages](https://git.archlinux.org/svntogit/packages.git/), [community packages](https://git.archlinux.org/svntogit/community.git/) and the repository of package customizations). 3. Read previous git revision numbers from files. @@ -30,7 +30,7 @@ The build system will consist from the following shell scripts: 7. Write the current git revision numbers to files. 8. Remove the lock file. -## build-packages +### build-packages 1. Read the build list and try to build the packages one by one. 2. Check if the current package or any of its dependencies are locked, broken or blocked (if a state file is available). 3. Create a state file for the current package and set it as locked. @@ -42,10 +42,10 @@ The build system will consist from the following shell scripts: 8. After a successful build, sign the package with the server's PGP key, and add (or upload) the binary package to the staging directory, together with a file which contains the git revision number. 9. Run db-update. -## arch32build +### arch32build Build the package in a clean chroot environment with a custom makefile.conf. -## db-update +### db-update 1. Create a lock file for build list. 2. Check if the git revision of the binary package is the same as on the build list. If it's different, then drop the package. Otherwise add binary packages to the proper repository. 3. Remove the package from the build list, and remove the corresponding package state file. -- cgit v1.2.3