Go to file
Jason Mehring 87d6284d67
Reworked the way template flavor files are found to allow flavors
- This better allows flavors to be within their own packages such as Whonix

The previous method of discovering flavor configurations was kind of broke
when using a flavor within a different package and including additional
options such as +standard.
2015-04-13 14:48:27 -04:00
appmenus_generic
prepared_images
qubeized_images
rpm
rpmbuild
tests Reworked the way template flavor files are found to allow flavors 2015-04-13 14:48:27 -04:00
.gitignore
appvm.buildlog
build_template_rpm
builder_fix_filenames
builder_setup
cleanup_image
create_template_list.sh
functions-name.sh
functions.sh Reworked the way template flavor files are found to allow flavors 2015-04-13 14:48:27 -04:00
Makefile
mount_root.sh
prepare_image
qubeize_image
README
templates.spec
umount_kill.sh
version

The Template Builder
======================

1) First, create a clean image of Fedora Linux install. You can use the fedoraize_image
script for this:

fedorize_image <image> <file-with-packets-lists>

NOTE: The fedorize_image script can be also used to update an image -- it
automatically assumes the update mode if the <image> already exists.

2) Update symlinks in rpms_to_install/ using the create_symlinks_in_rpms_to_install_dir.sh script. The script
reads the core, gui, and xen packages versions from version_{core,gui,xen} files and creates appropriate symlinks
in rpms_to_install/ dir.

Verify that all symlinks are correct.

3) Now, you can "qubeize" the image. This must be done as root. E.g.:

# ./qubeize_image <img> <template-name>

4) Finally, build the Template RPM (do it as normal user, not root), e.g.: 

$./build_rpm <name>

The resulting rpm is stored in rpm/noarch directory.