cookutils rev 59
doc + README: add info about build bot and cron as well as DB files in cache
author | Christophe Lincoln <pankso@slitaz.org> |
---|---|
date | Sat May 07 14:33:44 2011 +0200 (2011-05-07) |
parents | 540d8a5c1512 |
children | 107e1375ceef |
files | README doc/cookutils.en.html |
line diff
1.1 --- a/README Sat May 07 14:08:08 2011 +0200 1.2 +++ b/README Sat May 07 14:33:44 2011 +0200 1.3 @@ -75,6 +75,17 @@ 1.4 a nice way. A web interface also highlights success and error and can show 1.5 receipts and the cooker logs such as the last ordered list or commits check. 1.6 1.7 +Database files in the cache folder 1.8 + 1.9 + * activity : Activity information for the web interface 1.10 + * blocked : List of manually blocked packages 1.11 + * broken : Broken packages list when cook fail it is add here 1.12 + * commits : List of packages of the last commit check 1.13 + * cooklist : Cooklist for unbuild packages or custom command 1.14 + * cooknotes : All the notes added with 'cooker -n "My note" 1.15 + * installed* : Lists used to compare installed package before a package 1.16 + is cooked and after so we can remove them. 1.17 + 1.18 1.19 Toolchain 1.20 --------------------------------------------------------------------------------
2.1 --- a/doc/cookutils.en.html Sat May 07 14:08:08 2011 +0200 2.2 +++ b/doc/cookutils.en.html Sat May 07 14:33:44 2011 +0200 2.3 @@ -321,6 +321,18 @@ 2.4 # cooker notes 2.5 </pre> 2.6 2.7 +<h3>Cooker as a Build Bot</h3> 2.8 +<p> 2.9 + The Cooker is desingned to be a Built Bot for SliTaz, it means it monitor 2.10 + 2 woks, update the Hg wok, get the differencies and cook all packages that 2.11 + got a commit. To run The Cooker automatically you must use cron and add a 2.12 + single to root crontabs in /var/spool/cron/crontabs. Say you would like 2.13 + to run the Cooker each 2 hours: 2.14 +</p> 2.15 +<pre> 2.16 +*/2 * * * * /usr/bin/cooker 2.17 +</pre> 2.18 + 2.19 <!-- End content --> 2.20 </div> 2.21