SliTaz Pizza Help

Build process

First you have to choose the distro name, provide a short description, and a valid email address so Pizza can notify you when ISOs are built or in case the build failed. You must also choose a skeleton to base your custom distro on. Then add some packages and follow the steps. When validating the build, Pizza will create a tarball of your flavors and add it to the build queue so that the tarball file can be directly downloaded. When your flavor is built you will get a mail, it will be displayed on the Pizza main page and on the RSS feed.



SliTaz Pizza

The SliTaz Pizza provides tools and utils to build Live systems online.

	* Build ISO flavors online in a simple to use and modern interface
	* Use stable packages or cooking if near to a stable release
	* Build queue and one build at a time to be less resources intensive
	* Can be run locally as a frontend to Tazlito or from the cmdline
	* Produce standard and valid HTML code and wildly themable
	* Provide a status page to follow build process for each flavor
	* Create a tarball of the flavor receipt, list and addfiles
	* Log activities, build process and provide useful statistics
	* Keep ISO images and files public for a while, then archive them
	* Uniq ID strings for each flavor and mail notification
	* RSS feed for all newly built flavors and summary on web interface

Installation and Administration
Pizza uses a chroot to build ISOs and a web interface to create the flavor
file. Pizza can be installed and setup in a few commands. The package provides
a pizza host utility, pizza-bot build bot for chroot and pizza.cgi which is
the web interface main script. So let's go through the installation:

# tazpkg -gi slitaz-pizza

Or from Hg:

# hg clone
# cd pizza && make install

You can display a list of commands and a short usage with the usage command.
Create the chroot and build environment. You may want to have a look
at the Pizza configuration file before processing:

# pizza setup

Now you are ready to start the build bot to build queued flavors one by one.
You can also chroot in the environment to build manually or test:

# pizza start

In time there may be quite a lot of ISOs and temporary files. To clean up the
temporary files and old flavors files:

# pizza purge

The cron task is run in the chroot and checks if any flavors have been submitted,
by default it checks every 20 minutes. The bot frequency can be changed by
editing root crontabs in the build chroot.

To check the build queue or chroot manually you can use:

# pizza exec pizza-bot
# pizza chroot

Developers and translators
SHell script as you would expect. Keep speed in mind and security. Always
think to have a simple option and an advanced option, for example in rootfs
modification let users add custom wallpaper easily and advanced users to
upload a full rootfs.

Pizza has been coded from the beginning with gettext support. Please forget
'echo' and use gettext, but remember that gettext "" is equivalent to echo -n.
To start a new translation please use msginit from the pot file directory.
Example for French/France locale (fr_FR):

	$ msginit -l fr_FR -o fr.po -i pizza.pot