# HG changeset patch # User Paul Issott # Date 1238238836 0 # Node ID 864829b32e9a5f1a6b238143fd7afd4a227f7696 # Parent 0a45c573b38c28b4bf42968aff72a22701b71729 en: Edit Cookbook (quick) diff -r 0a45c573b38c -r 864829b32e9a en/doc/cookbook/build-host.html --- a/en/doc/cookbook/build-host.html Sat Mar 28 01:45:51 2009 +0100 +++ b/en/doc/cookbook/build-host.html Sat Mar 28 11:13:56 2009 +0000 @@ -49,7 +49,7 @@ @@ -57,44 +57,39 @@

Using scripts: /home/slitaz/scripts

-To help maintaining the mirror, flavors and other services some scripts -are used, there are mostly all configured for the cooking version. To +To help maintain the mirror, flavors and other services, some scripts +are used. They are mostly all configured for the cooking version. To add them to your default path:

-
- $ echo 'export PATH=/home/slitaz/scripts:$PATH' >> ~/.profile
+
 $ echo 'export PATH=/home/slitaz/scripts:$PATH' >> ~/.profile
 

 

-Each script should have a small help and description, if none, just open
-it:
+Each script should have a tiny help file and description, if not, just open:
 

-
- $ cd /home/slitaz/script && ls
+
 $ cd /home/slitaz/script && ls
  $ ./script.sh help
 

 
 
 
Cooking undigest packages

 

-You can use the undigest wok in the chroot environement to cook some
+You can use the undigest wok in the chroot environment to cook some
 non supported packages. If you maintain official packages and they cook
-succefully on tank you can test it on your local machine and then commit
+successfully on tank, then you can test on your local machine and commit
 in the official wok. Mirror maintainers will then rebuild and upload the
 packages on mirror.slitaz.org.
 

 

-To build packages in the undigest wok and in the chroot environement, 
-some commands are better than a long text:
+To build packages in the undigest wok and in the chroot environment:
+commands are sometimes better than a long text:
 

-
- $ ln -s /home/slitaz/cooking/chroot/home/undigest .
+
 $ ln -s /home/slitaz/cooking/chroot/home/undigest .
 

 

-You can copy file with gFTP-sftp-scp directly in the wok or from the 
+You can copy files with gFTP-sftp-scp directly into the wok or from the 
 current directory:
 

-
- $ cp -a package undigest/wok
+
 $ cp -a package undigest/wok
  $ su -c chroot.sh
  /# cd home/undigest
  /# tazwok cook package
@@ -105,49 +100,45 @@
 
 
Cooking official packages

 

-Mirror maintainers have root access and some have write access to the
+Maintainers have root access and some have write access to the
 main mirror at mirror.slitaz.org, if you want to help in this task please 
-contact one of the most active developpers (check hg repos).
+contact one of the active developers (check hg repos).
 

 

-Everything is cook in a chroot environement, default path for the main
-wok is /home/slitaz, some changes can be done directly in this wok, the
+Everything is cooked in a chroot environment, the default path for the main
+wok is /home/slitaz. Some changes can be made directly in this wok: the
 real Hg is out of the chroot and copied in the chroot with wok.sh:
 

-
- # wok.sh hgup
+
 # wok.sh hgup
  # chroot.sh
 

 

 Cook all missing packages, one by one or with 'tazwok cmp --cook', note
-that comparaison it not requiert, if you know witch packages you must
+that comparison (cmp) it not required, if you know which packages to
 cook:
 

-
- /# tazwok cmp
+
 /# tazwok cmp
  /# tazwok cook package-name
 

 

-Remove all old packages and then rebuild the lists:
+Remove all the old packages and then rebuild the lists:
 

-
- /# tazwok cmp --remove
+
 /# tazwok cmp --remove
  /# tazwok gen-list --text
  /# exit
 

 

 If you have write access to the mirror you can make a dry-push to check
-and then upload, push will also remove old packages on the mirror.
+and then upload; push will also remove any old packages on the mirror.
 

 
 
 
Stable packages

 

-Packages for the stable release are build in a chroot environement like
-the Cooking packages.
+Packages for the stable release are also built in a chroot environment like
+the Cooking packages:
 

-
- # chroot.sh stable
+
 # chroot.sh stable
 

 
 
@@ -155,18 +146,16 @@
 

 Mirror maintainers can upload by hand with the script mirror.sh:
 

-
- # mirror.sh help
+
 # mirror.sh help
 

 
 
 
Update website by hand

 

-Wesite and packages web interface are updated nightly by cron and can
-also be update by hand (used the day of release for example):
+The Website and packages web interface are updated nightly by cron and can
+also be updated by hand (used on the day of release for example):
 

-
- # website.sh up
+
 # website.sh up
  # website.sh help
 

 
diff -r 0a45c573b38c -r 864829b32e9a en/doc/cookbook/index.html
--- a/en/doc/cookbook/index.html	Sat Mar 28 01:45:51 2009 +0100
+++ b/en/doc/cookbook/index.html	Sat Mar 28 11:13:56 2009 +0000
@@ -34,7 +34,7 @@
 
    
 	
  • Wok & Tools - SliTaz Package Tools.
    • 
 	
  • Receipts - Receipts for creating SliTaz packages.
    • 
-	
  • Build Host - SliTaz Buils host (tank).
    • 
+	
  • Build Host - SliTaz Build host (tank).
    • 
 	
  • Boot Scripts - The startup and shutdown scripts.
    • 
 	
  • SliTaz Tools - The Toolbox.
    • 
 	
  • Release Tasks - List of things to do before publishing a new version (Cooking or stable).
    • 
diff -r 0a45c573b38c -r 864829b32e9a en/doc/cookbook/reltasks.html
--- a/en/doc/cookbook/reltasks.html	Sat Mar 28 01:45:51 2009 +0100
+++ b/en/doc/cookbook/reltasks.html	Sat Mar 28 11:13:56 2009 +0000
@@ -37,29 +37,29 @@
 
    Check list
    
 
      
 	
    • Release version is specified by /etc/slitaz-release, this file
-	is contrôled by slitaz-base-files. Base files are tageg just before
-	a stable reale to chage the version string and let Tazpkg use the new
-	pacpages.
      • 
+	is controlled by slitaz-base-files. Base files are tagged just before
+	a stable release to change the version string and let Tazpkg use the new
+	packages.
 	
    • Check that the SliTaz version specified in /etc/issue message is 
-	the same as displayed in the isolinux.msg.
      • 
+	the same as displayed in isolinux.msg.
 	
    • Add and check that documents and images are in the root of the CD - ie.
 	README, index.html, style.css and the directory of images. All files are
 	in the slitaz-tools archive; just copy the addfiles/ and        
 	regenerate the ISO.
      • 
 	
    • Test, test, and test ...
      • 
-	
    • Prepare the website announcement and RSS feeds. Mailing list is used
-	for translation and texte should be send 1 or 2 days before release.
      • 
+	
    • Prepare the website announcement and RSS feeds. The Mailing list is used
+	for translation and any text should be submitted 1 or 2 days before release.
      • 
 
    
 
 
    Stable documentation
    
 
    
-SliTaz stable release provide the release notes on the LiveCD trought
-the package slitaz-doc, the repos is tagged just before release
-and archived on the mirror. After the wok have been copied to wok-stable
-the doc are back to a cooking cycle and just provide and index with basic
-information. On the system doc are located in: /usr/share/doc/slitaz, a 
-desktop file and icon are provide in the sources package and can be used
-to have a qick access to documentation.
+SliTaz stable release provides the release notes on the LiveCD through
+the package slitaz-doc, the repos are tagged just before release
+and are archived on the mirror. After the wok have been copied to wok-stable,
+the docs are back to a cooking cycle and just provide an index with basic
+information. On the system, docs are located in: /usr/share/doc/slitaz, a 
+desktop file and icon are provided in the sources package and can be used
+to have quick access to the documentation.