SliTaz Repositories

     1.1 --- a/cook	Tue May 17 15:35:42 2011 +0200
     1.2 +++ b/cook	Tue May 17 20:50:05 2011 +0100
     1.3 @@ -441,8 +441,8 @@
     1.4  		for i in $dep $implicit
     1.5  		do
     1.6  			if [ ! -f "$INSTALLED/$i/receipt" ]; then
     1.7 -				# Try local package first. In some case implicit dont exist, ex:
     1.8 -				# libboost-dev exist but not libboost, so check if we got vers.
     1.9 +				# Try local package first. In some cases implicit doesn't exist, ex:
    1.10 +				# libboost-dev exists but not libboost, so check if we got vers.
    1.11  				unset vers
    1.12  				vers=$(grep ^VERSION $WOK/$i/receipt 2>/dev/null | cut -d '"' -f 2)
    1.13  				if [ -f "$PKGS/$i-$vers.tazpkg" ]; then

     2.1 --- a/doc/cookutils.en.html	Tue May 17 15:35:42 2011 +0200
     2.2 +++ b/doc/cookutils.en.html	Tue May 17 20:50:05 2011 +0100
     2.3 @@ -35,7 +35,7 @@
     2.4  <p>
     2.5  	Cook provides a small built-in help usage that you can display with the
     2.6  	command 'usage'. It also has some options to perform special tasks on
     2.7 -	a package before cooking it or after. To get help and usage:
     2.8 +	a package before cooking it or afterwards. To get help and usage:
     2.9  </p>
    2.10  <pre>
    2.11  # cook usage
    2.12 @@ -56,7 +56,7 @@
    2.13  	can specify a custom path in the argument. The chroot location is not
    2.14  	important, when you will be in the chroot you will use standard SliTaz
    2.15  	paths such as /home/slitaz/wok for the wok directory or /home/slitaz/log
    2.16 -	for all the cook logs. As usual you can diplay tazdev help usage with:
    2.17 +	for all the cook logs. As usual you can display tazdev help usage with:
    2.18  	tazdev usage.
    2.19  </p>
    2.20  <p>
    2.21 @@ -94,9 +94,9 @@
    2.22  <h3>Test your environment</h3>
    2.23  <p>
    2.24  	Cook provides a test command which will create a package and cook it. This lets
    2.25 -	you see if your enviroment is working and it provides an example package with
    2.26 +	you see if your environment is working and it provides an example package with
    2.27  	a receipt. The dummy package is named 'cooktest' and can be removed after
    2.28 -	testing. To cook the cooktest:
    2.29 +	testing. To cook the test package:
    2.30  </p>
    2.31  <pre>
    2.32  # cook test
    2.33 @@ -104,7 +104,7 @@
    2.34  
    2.35  <h3>Create and cook</h3>
    2.36  <p>
    2.37 -	If you environment is setup corectly you can start creating and compiling
    2.38 +	If your environment is setup correctly you can start creating and compiling
    2.39  	SliTaz packages from your wok. To create a new package with an empty receipt:
    2.40  </p>
    2.41  <pre>
    2.42 @@ -112,14 +112,14 @@
    2.43  </pre>
    2.44  <p>
    2.45  	If you have just created a new package, you'll have to edit the receipt with your
    2.46 -	favorite text editor. When the receipt is ready or if you have existing
    2.47 -	packages, you can cook it:
    2.48 +	favorite text editor. When the receipt is ready or if you have an existing
    2.49 +	package, you can cook it:
    2.50  </p>
    2.51  <pre>
    2.52  # cook pkgname
    2.53  </pre>
    2.54  <p>
    2.55 -	If all went well you will find your packages in the $SLITAZ/packages
    2.56 +	If all went well you will find your package in the $SLITAZ/packages
    2.57  	directory and any produced files in $SLITAZ/wok/pkgname.
    2.58  </p>
    2.59  
    2.60 @@ -218,7 +218,7 @@
    2.61  # cooker setup
    2.62  </pre>
    2.63  <p>
    2.64 -	If all went well you have now 2 woks, base developement packages installed
    2.65 +	If all went well you now have 2 woks, base development packages installed
    2.66  	and all needed files created. The default behavior is to check for commits,
    2.67  	you can run a test:
    2.68  </p>
    2.69 @@ -232,7 +232,7 @@
    2.70  	cooker without any arguments or cook packages manually. The cooker lets you
    2.71  	cook a single package or all packages of a category or a flavor. You can also
    2.72  	try to build all unbuilt packages, but be aware the Cooker was not designed
    2.73 -	to handle thousand of packages.
    2.74 +	to handle thousands of packages.
    2.75  </p>
    2.76  <p>
    2.77  	To cook a single package which is the same as 'cook pkgname' but with more
    2.78 @@ -253,7 +253,7 @@
    2.79  # cooker cat [category]
    2.80  </pre>
    2.81  <p>
    2.82 -	The Cooker lets you also recook a specific Hg revision. It useful in
    2.83 +	The Cooker lets you also recook a specific Hg revision. It's useful in
    2.84  	production so that if the Build Bot was interrupted while cooking commits, you
    2.85  	can then cook packages manually:
    2.86  </p>
    2.87 @@ -359,10 +359,10 @@
    2.88  <p>
    2.89  	The Cooker environment and cron task can automatically be started at boot time.
    2.90  	You must have the cookutils-daemon installed on the host and use a standard SliTaz
    2.91 -	to make it work properly (cooking goes in /home/slitaz/cooking). The daemon
    2.92 -	script will mount any virtual filesystems if needed as well as source and
    2.93 -	packages. Sources files are in /home/slitaz/src and bound into the chroot
    2.94 -	so you can share packages sources between several versions (stable, cooking,
    2.95 +	installation to make it work properly (cooking goes in /home/slitaz/cooking). The 
    2.96 +	daemon script will mount any virtual filesystems if needed as well as source and
    2.97 +	packages. Source files are in /home/slitaz/src and bound into the chroot
    2.98 +	so you can share package's sources between several versions (stable, cooking,
    2.99  	undigest). If the package is not yet installed:
   2.100  </p>
   2.101  <pre>