SliTaz GNU/Linux official and community documentation wiki.


This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:cookbook:buildhost [2010/07/08 17:14] external edit
en:cookbook:buildhost [2017/04/25 19:32] (current)
Line 1: Line 1:
 ====== SliTaz Build Host (tank) ====== ====== SliTaz Build Host (tank) ======
-SliTaz build host info and howto. ​+SliTaz build host info and howto.
 ===== Folders in: /​home/​slitaz ===== ===== Folders in: /​home/​slitaz =====
Line 7: Line 7:
     * cooking/ - Cooking chroot and flavors.     * cooking/ - Cooking chroot and flavors.
     * stable/ - Stable tree.     * stable/ - Stable tree.
 +    * undigest/ - Undigest tree.
     * repos/ - All the project repos (where the commits are pushed).     * repos/ - All the project repos (where the commits are pushed).
-    * www/ - Virtual hosts (website, hg, boot, people, etc).+    * www/ - Virtual hosts (boot, people, etc).
 ===== Using tazdev ===== ===== Using tazdev =====
Line 18: Line 19:
 </​code>​ </​code>​
-===== Cooking ​undigest ​packages =====+===== Cooking ​official ​packages =====
-You can use the undigest wok in the chroot environment ​to cook some non supported packages. If you maintain official packages and they cook 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 have root access and some have write access ​to the main mirror at, if you want to help in this task please contact one of the active developers (check hg repos).
-To build packages ​in the undigest ​wok and in the chroot ​environment:​ commands are sometimes better than a long text:+Everything is cooked ​in a chroot environment, ​the default path for the build wok is /​home/​slitaz/​cooking/​chroot. No changes must be done in the chroot ​and don't install any packages to keep it clean. We run the cooking chroot under tty4:
 <​code>​ <​code>​
- $ ln -s /​home/​slitaz/​cooking/​chroot/​home/​undigest .+ # conspy ​-f 4
 </​code>​ </​code>​
-You can copy files with gFTP-sftp-scp directly into the wok or from the current directory:+<note tip>Dont forget to update the chroot ​with //tazpkg up -r//</​note>​
-<​code>​ +In the event of reboot or trouble ​you may be prompted ​to a login, login as root then use '​tazdev ​chroot' to chroot into the build envTo cook all the last committed packages or cook a single package:
- $ cp -package undigest/​wok +
- $ su -c "​tazdev chroot"​ +
- /# cd home/​undigest +
- /# tazwok cook package +
- /# exit +
- $ ls undigest/​packages +
-</​code>​ +
- +
-===== Cooking official packages ===== +
- +
-Maintainers have root access and some have write access to the main mirror at,​ if you want to help in this task please contact one of the active developers (check hg repos). +
- +
-Everything is cooked in a chroot ​environment,​ the default path for the build wok is $CHROOT/​home/​slitaz/​wokSome changes can be made directly in this wok: the real Hg is copied into the chroot by tazbb (Build Bot). To chroot in cooking:+
 <​code>​ <​code>​
- # ​tazdev chroot+ /cooker 
 + /# cooker pkg pkgname
 </​code>​ </​code>​
-Cook all the last commited packages or cook everything with '​cook-all',​ note that comparison it not required if you know which packages to cook. If you want to force the cooking of some of the packages by tazbb, you can then clean with tazwok. By default tazbb cooks only the last commit:+To get out of conspy press [ESC] 3x times, don't exit the chroot. If you have write access ​to the mirror, you can make a dry-push to check and then upload; push will also remove any old packages on the mirror.
-<​code>​ +===== Cooking undigest packages =====
- /# tazbb cook-commit +
-If needed (tazbb does this automatically)you can remove all the old packages and then rebuild the lists manually:+On Tank we run the undigest cooker under tty6using conspy:
 <​code>​ <​code>​
- /tazbb clean-up + $ su 
- /tazwok gen-list --text + conspy ​-f 6 
- /exit+ # ​cooker 
 + or 
 + # ​cooker pkg pkgname
 </​code>​ </​code>​
-If you have write access to the mirror, you can make a dry-push to check and then upload; push will also remove any old packages on the mirror. 
 ===== Stable packages ===== ===== Stable packages =====
Line 70: Line 57:
 <​code>​ <​code>​
- # ​tazdev chroot stable+ # ​conspy -f 2
 </​code>​ </​code>​
Line 81: Line 68:
 </​code>​ </​code>​
-===== Update website by hand ======+===== Recreate a chroot ​======
-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):+If a chroot seems broken or needs to be rebuilt. Exit the chroot and unmount the virtual system (/home is keptas root. From the corresponding conspy session:
 <​code>​ <​code>​
- # tazdev ​update-www+ # tazdev ​clean-chroot 
 + # tazdev gen-chroot 
 + # tazdev chroot 
 + /# tazpkg recharge 
 + /# cook setup 
 + /# cooker
 </​code>​ </​code>​
en/cookbook/buildhost.1278602056.txt.gz · Last modified: 2012/02/22 20:25 (external edit)