SliTaz Repositories

     1.1 --- a/cooker	Tue May 10 15:55:01 2011 +0200
     1.2 +++ b/cooker	Tue May 10 19:36:19 2011 +0100
     1.3 @@ -349,7 +349,7 @@
     1.4  		separator
     1.5  		
     1.6  		# Find all unbuilt packages. Get EXTRAVERSION from packed receipt
     1.7 -		# if exist since extra version is add when packing the package.
     1.8 +		# if it exists since extra version is added when packing the package.
     1.9  		echo "Searching for all unbuilt packages" | log
    1.10  		for pkg in *
    1.11  		do
    1.12 @@ -386,8 +386,8 @@
    1.13  		echo "Cooker PID   : $$" | log_commits
    1.14  		echo "Cooker date  : $(date '+%Y-%m-%d %H:%M:%S')" | log_commits
    1.15  		
    1.16 -		# Get revisions. Here we have 2 echo since we want msg on screen,
    1.17 -		# in commits log and activity DB without space before :
    1.18 +		# Get revisions. Here we have 2 echoes since we want a msg on screen,
    1.19 +		# in commits log and activity DB without a space before.
    1.20  		cd $wok || exit 1
    1.21  		cur=$(hg head --template '{rev}\n')
    1.22  		echo "Updating wok : ${wok}-hg (rev $cur)" | log_commits

     2.1 --- a/doc/cookutils.en.html	Tue May 10 15:55:01 2011 +0200
     2.2 +++ b/doc/cookutils.en.html	Tue May 10 19:36:19 2011 +0100
     2.3 @@ -310,7 +310,7 @@
     2.4  <p>
     2.5  	Note: It's not obligatory to install the cookutils on your host to use the
     2.6  	web interface, you can also copy the cooker.cgi and style.css files for
     2.7 -	example in your ~/Public directory and use a custom cook.conf with it. The
     2.8 +	example into your ~/Public directory and use a custom cook.conf with it. The
     2.9  	advantage of installing cookutils on the host is to get regular updates via
    2.10  	the Tazpkg packages manager. Say you have cloned or downloaded the cookutils:
    2.11  </p>