From c15dacca643833aa3021a33c536a25f9b6cb0c58 Mon Sep 17 00:00:00 2001 From: deep-42-thought Date: Tue, 6 Jun 2017 15:20:35 +0200 Subject: Updated Build system (markdown) --- Build-system.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Build-system.md b/Build-system.md index a01e642..02823d6 100644 --- a/Build-system.md +++ b/Build-system.md @@ -23,9 +23,9 @@ The build system will consist from the following shell scripts: - return-assignment: add binary packages to the repository, and remove them from the build list (could have been a fork of [db-update](https://git.archlinux.org/dbscripts.git/tree/db-update), but isn't) ### 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. +1. 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). +2. Read previous git revision numbers from files. +3. Create a lock file for build list. 4. Check modified packages from the last update, and put them to the build list. If a package is updated, but already on the rebuild list, then just update the git revision number. If a package is deleted, remove from the rebuild list, and add it to the deletion list. If a new package is added, then ensure that it's not on the deletion list. 6. Put the list in the proper build order. 7. Write the current git revision numbers to files. -- cgit v1.2.3