summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSuren A. Chilingaryan <csa@suren.me>2019-09-03 01:35:59 +0200
committerSuren A. Chilingaryan <csa@suren.me>2019-09-03 01:35:59 +0200
commit049e7af95d6211223642b8243d68056cc24137f7 (patch)
tree4e4b4f5fd6a1e5de5d125e585a442942aeda1975
parent9ee658cba222c4141d90f868a45ac3718d655852 (diff)
downloadgentoo-builder-049e7af95d6211223642b8243d68056cc24137f7.tar.gz
gentoo-builder-049e7af95d6211223642b8243d68056cc24137f7.tar.bz2
gentoo-builder-049e7af95d6211223642b8243d68056cc24137f7.tar.xz
gentoo-builder-049e7af95d6211223642b8243d68056cc24137f7.zip
Explain the idea in README
-rw-r--r--README18
1 files changed, 14 insertions, 4 deletions
diff --git a/README b/README
index 2f9e115..9734d17 100644
--- a/README
+++ b/README
@@ -24,9 +24,19 @@ Idea:
- Start building
make build
make logs
+
-
- It will build packages and put it on the attached volume. If crashed and restarted, he will first re-use already
- built binaries and, then, will continue compilling. This requires fast storage and will not play well with overlayfs.
- I guess lvm based stuff is necessety.
+ It will build packages and put it on the attached volume. The script is designed to run forever.
+ * If crashed it will start idle sleep until the connected user solves the problem and kills the
+ sleep. It will restart building, then.
+ * If it finishes, it will re-sync after given interval or just wait until the user triggers rebuild
+ manually, again by killing sleep.
+
+ If the script is restarted for some reason (crash/server reboot), emerge will first re-use already
+ built binaries and, then, will continue compilling.
+ * At some point a snapshot could be made by converting 'container' into the huge 'image' with
+ 'docker commit'.
+
+
+ - Overall: This requires fast. I guess lvm based stuff is necessety.