|author||deep-42-thought <firstname.lastname@example.org>||2017-06-08 09:37:48 +0200|
|committer||deep-42-thought <email@example.com>||2017-06-08 09:37:48 +0200|
Updated Build system (markdown)
1 files changed, 2 insertions, 1 deletions
diff --git a/Build-system.md b/Build-system.md
index d5a4dcf..885d161 100644
@@ -2,7 +2,8 @@ The build system is the heart of the project. On this page you can see the initi
## Files in git repository
For packages that need some customizations, the build system will use a repository that consist from the following files:
-- _[package_name]_/_[architecture_name]_.sh: shell script, which will run in the same directory where the original PKGBUILD found. It can do the following things: apply sed lines, apply patches, or even replace the original PKGBUILD file with a custom one.
+- _[repository]_/_[package_name]_/PKGBUILD: This file will be appended to the original PKGBUILD, therefore any variables and functions can be overwritten.
+- _[repository]_/_[package_name]_/_[other_files]_: These files will be copied to the original directory, overwriting any existing file there.
- blacklist: text file, list of packages that will be ignored by the build system (e.g. cannot build for this architecture).
- build-manually: text file, list of packages that will be added to the build list on update, but need manual interaction before build. Packages that depend on this package will be also hold back.
- update-once: text file, list of packages that will be updated next time even if nothing changed. This list will be cleared out on next update. This list overrides the 'build-manually' list.