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
Joanna Rutkowska 4c1c6e7bab
R2-Beta2
11 years ago
3rd_party_software
appmenus_fc17
appmenus_fc18
appmenus_generic
base_rpms_fc13
base_rpms_fc14
base_rpms_fc15
base_rpms_fc16
base_rpms_fc17
base_rpms_fc18
clean_images
fedorized_images
keys_fc13
keys_fc14
keys_fc15
keys_fc16
keys_fc17
keys_fc18
mnt
qubeized_images
rpm
rpmbuild
yum_repo_qubes
.gitignore
Makefile
README
add_3rd_party_software.sh
appvm.buildlog
build_template_rpm
cleanup_image
comps-qubes-template.xml
convert_app2template.sh
create_apps_templates.sh
fedorize_image
mount_root.sh
qubeize_image
templates.spec
version
yum.conf

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.