SliTaz build host info and howto.
- cooking/ - Cooking chroot and flavors.
- stable/ - Stable tree.
- undigest/ - Undigest tree.
- repos/ - All the project repos (where the commits are pushed).
- www/ - Virtual hosts (boot, people, etc).
To help maintain the mirror, flavors and other services, the tazdev command is used. It is mostly configured for the cooking version. Usage:
$ tazdev usage
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 active developers (check hg repos).
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:
# conspy -f 4
In the event of a reboot or trouble you may be prompted to a login, login as root then use 'tazdev chroot' to chroot into the build env. To cook all the last committed packages or cook a single package:
/# cooker /# cooker pkg pkgname
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.
On Tank we run the undigest cooker under tty6, using conspy:
$ su # conspy -f 6 # cooker or # cooker pkg pkgname
Packages for the stable release are also built in a chroot environment like the Cooking packages:
# conspy -f 2
Mirror maintainers can upload by hand with tazdev (-dp for a dry push):
# tazdev -p $USER
If a chroot seems broken or needs to be rebuilt. Exit the chroot and unmount the virtual system (/home is kept) as root. From the corresponding conspy session:
# tazdev clean-chroot # tazdev gen-chroot # tazdev chroot /# cook setup /# cooker