You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Go to file
Marek Marczykowski-Górecki f1b1258631
version 2.1.9
9 years ago
appmenus_generic
prepared_images
rpm
rpmbuild
tests
.gitignore Add support for plugins, move all distribution-specific code there 9 years ago
Makefile Add support for plugins, move all distribution-specific code there 9 years ago
README
appvm.buildlog
build_template_rpm Add support for plugins, move all distribution-specific code there 9 years ago
builder_fix_filenames
builder_setup Add support for plugins, move all distribution-specific code there 9 years ago
cleanup_image
create_template_list.sh
functions-name.sh
functions.sh Provide chroot() wrapper also in quiet mode 9 years ago
mount_root.sh
prepare_image Add support for plugins, move all distribution-specific code there 9 years ago
qubeize_image Add support for plugins, move all distribution-specific code there 9 years ago
templates.spec Add workaround for bug in qvm-sync-appmenus 9 years ago
umount_kill.sh
version version 2.1.9 9 years ago

README

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.