d13a4eff88
The whole build process is started as root (check Makefile), so there is no need for additional sudo. This makes some things much simpler (for example appending to some files). |
||
---|---|---|
appmenus_fc17 | ||
appmenus_fc18 | ||
appmenus_generic | ||
base_rpms_fc18 | ||
clean_images | ||
mnt | ||
prepared_images | ||
qubeized_images | ||
rpm | ||
rpmbuild | ||
scripts_archlinux | ||
scripts_fedora | ||
yum_repo_qubes | ||
.gitignore | ||
appvm.buildlog | ||
build_template_rpm | ||
builder_setup | ||
cleanup_image | ||
comps-qubes-template.xml | ||
convert_app2template.sh | ||
create_apps_templates.sh | ||
Makefile | ||
mount_root.sh | ||
prepare_image | ||
qubeize_image | ||
README | ||
templates.spec | ||
version | ||
yum.conf |
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.