# HG changeset patch
# User Aleksej Bobylev <al.bobylev@gmail.com>
# Date 1450360691 -7200
# Node ID 02dfb02ecb566b876362a630d94a3312c6acb756
# Parent  247563705078560342c9de1237e8cac146af8c96
Up: tazpkg(890), cookutils(788)

diff -r 247563705078 -r 02dfb02ecb56 cookutils-daemon/receipt
--- a/cookutils-daemon/receipt	Thu Dec 17 13:30:03 2015 +0100
+++ b/cookutils-daemon/receipt	Thu Dec 17 15:58:11 2015 +0200
@@ -1,7 +1,7 @@
 # SliTaz package receipt.
 
 PACKAGE="cookutils-daemon"
-VERSION="786"
+VERSION="788"
 CATEGORY="system-tools"
 SHORT_DESC="SliTaz Cooker daemon script for build host."
 MAINTAINER="pankso@slitaz.org"
diff -r 247563705078 -r 02dfb02ecb56 cookutils/description.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/cookutils/description.txt	Thu Dec 17 15:58:11 2015 +0200
@@ -0,0 +1,47 @@
+The SliTaz Cookutils provide tools and utils to build SliTaz packages.
+
+
+Cook
+----
+
+The cook tool should be used in a chroot environment: simply use the command
+`tazdev gen-chroot` to build one. You can also build packages directly but
+build deps will not be handled correctly since cook will install missing
+packages to perform a build and then remove them only if they were not
+installed before, this way we can keep a clean build environment.
+
+We use standard SliTaz paths to work such as /home/slitaz/wok, if you work on
+cooking from stable or want to keep a clean system: create a chroot.
+
+
+Cooker
+------
+
+The Cooker is a Build Bot which automates the build process but doesn't make
+the dinner for you! We need quality receipts to cook successfully and the goal
+is not to have a bloated script so please Keep It Short and Simple.
+
+The web interface consists of one CGI script and one CSS style. Cook logs can
+be produced by cook and the cooker just acts as a fronted to check them in
+a nice way. A web interface also highlights success and error and can show
+receipts and the cooker logs such as the last ordered list or commits check.
+
+
+Cookiso
+-------
+
+Cookiso is the official tool to automate the ISO build. The goal is to provide
+a simple to use, rock solid tool with a web interface à la Cooker. It shares
+configuration and templates with the Cooker but can be run on its own so it
+can be used by contributors or customers to automate custom ISO building.
+Cookiso must be run in a chroot which can be the same chroot as the Cooker.
+
+
+Cross compiling
+---------------
+
+Cookutils lets you cross compile a package for a specific architecture. Say you
+want to build ARM binaries from a standard i486 machine. Cookutils provides
+helpers for the ARM platform, but the first thing to do is compile a cross
+toolchain and modify the main cook.conf variables to use the correct ARCH,
+CFLAGS and BUILD_SYSTEM
diff -r 247563705078 -r 02dfb02ecb56 cookutils/receipt
--- a/cookutils/receipt	Thu Dec 17 13:30:03 2015 +0100
+++ b/cookutils/receipt	Thu Dec 17 15:58:11 2015 +0200
@@ -1,7 +1,7 @@
 # SliTaz package receipt.
 
 PACKAGE="cookutils"
-VERSION="786"
+VERSION="788"
 CATEGORY="base-system"
 SHORT_DESC="SliTaz packages builder new generation."
 MAINTAINER="pankso@slitaz.org"
diff -r 247563705078 -r 02dfb02ecb56 tazpkg/receipt
--- a/tazpkg/receipt	Thu Dec 17 13:30:03 2015 +0100
+++ b/tazpkg/receipt	Thu Dec 17 15:58:11 2015 +0200
@@ -1,7 +1,7 @@
 # SliTaz package receipt.
 
 PACKAGE="tazpkg"
-VERSION="889"
+VERSION="890"
 CATEGORY="base-system"
 SHORT_DESC="SliTaz packages manager"
 MAINTAINER="pankso@slitaz.org"