rBuilder Online:Compressed Tar File
From rPath Wiki
The Compressed Tar File image build type in rBuilder creates the entire directory tree of your software appliance and to compresses it into a single file (.tar.gz file, also known as a "tarball"). The tar, or archive, consists of the file tree of the installed appliance. These files can be uncompressed onto an existing filesystem.
Use this image type to copy the appliance's file tree onto a local filesystem for examining its contents. Also use this for creating a Xen DomU when the filesystem size and structure can be arbitrary.
When building the appliance group to use this image type, the specifications required are those specific to deploying as a Xen DomU (when applicable) and the architecture of the destination system (32-bit or 64-bit). The following rMake command is used to build group-example Xen DomU for both 32-bit and 64-bit architectures:
$> rmake build 'group-example[xen, domU is: x86]' 'group-example[xen, domU is: x86_64]'
The following options can be customized in the Advanced Options section when creating a build of this build type.
- Custom output filename prefix
- Use this to specify a custom prefix for filenames output from the build, overriding the default name-version-architecture prefix.
- Custom Conary installLabelPath setting
- Use this to specify the locations where your software appliance will retrieve software updates, such as a local Conary repository dedicated to the development of your software appliance. (If you do not choose this option, the install label paths are set to locations at rpath.org.)
- Automatically install required dependencies during updates
- Use this if you want the appliance to automatically install additional software on which updates may depend.
- How many MB swap space should be reserved in this image?
- Use this to designate a size for the swap file in the filesystem that best meets the needs of your software appliance. The default value for this is 128 MB.