7c37e25aa1
The actual version of core, gui, and xen packages to use are given in version_{core,gui,xen} files |
||
---|---|---|
appmenus | ||
base_rpms | ||
clean_images | ||
fedorized_images | ||
keys | ||
mnt | ||
qubeized_images | ||
rpm | ||
rpms_3rd_party | ||
rpms_to_install | ||
vm_conf_files | ||
.gitignore | ||
add_3rd_party_software.sh | ||
appvm.buildlog | ||
build_template_rpm | ||
cleanup_image | ||
create_apps_for_templatevm.sh | ||
create_apps_templates.sh | ||
create_symlinks_in_rpms_to_install_dir.sh | ||
dispvm-dotfiles.tbz | ||
fedorize_image | ||
mount_root.sh | ||
qubeize_image | ||
README | ||
templates.spec | ||
version | ||
version_core | ||
version_gui | ||
version_xen |
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.