97c01e48ed
Currently we have all our elements and library files in a top-level directory and install them into <root>/share/diskimage-builder/[elements|lib] (where root is either / or the root of a virtualenv). The problem with this is that editable/development installs (pip -e) do *not* install data_files. Thus we have no canonical location to look for elements -- leading to the various odd things we do such as a whole bunch of guessing at the top of disk-image-create and having a special test-loader in tests/test_elements.py so we can run python unit tests on those elements that have it. data_files is really the wrong thing to use for what are essentially assets of the program. data_files install works well for things like config-files, init.d files or dropping documentation files. By moving the elements under the diskimage_builder package, we always know where they are relative to where we import from. In fact, pkg_resources has an api for this which we wrap in the new diskimage_builder/paths.py helper [1]. We use this helper to find the correct path in the couple of places we need to find the base-elements dir, and for the paths to import the library shell functions. Elements such as svc-map and pkg-map include python unit-tests, which we do not need tests/test_elements.py to special-case load any more. They just get found automatically by the normal subunit loader. I have a follow-on change (I69ca3d26fede0506a6353c077c69f735c8d84d28) to move disk-image-create to a regular python entry-point. Unfortunately, this has to move to work with setuptools. You'd think a symlink under diskimage_builder/[elements|lib] would work, but it doesn't. [1] this API handles stuff like getting files out of .zip archive modules, which we don't do. Essentially for us it's returning __file__. Change-Id: I5e3e3c97f385b1a4ff2031a161a55b231895df5b
36 lines
1.3 KiB
ReStructuredText
36 lines
1.3 KiB
ReStructuredText
========
|
|
Gentoo
|
|
========
|
|
Use a Gentoo cloud image as the baseline for built disk images. The images are
|
|
located in profile specific sub directories:
|
|
|
|
http://distfiles.gentoo.org/releases/amd64/autobuilds/
|
|
|
|
As of this writing, only x86_64 images are available.
|
|
|
|
Notes:
|
|
|
|
* There are very frequently new automated builds that include changes that
|
|
happen during the product maintenance. The download directories contain an
|
|
unversioned name and a versioned name. The unversioned name will always
|
|
point to the latest image, but will frequently change its content. The
|
|
versioned one will never change content, but will frequently be deleted and
|
|
replaced by a newer build with a higher version-release number.
|
|
|
|
* In order to run the package-installs element you will need to make sure
|
|
`dev-python/pyyaml` is installed on the host.
|
|
|
|
* In order to run the vm element you will need to make sure `sys-block/parted`
|
|
is installed on the host.
|
|
|
|
* Other profiles can be used by exporting GENTOO_PROFILE with a valid profile.
|
|
A list of valid profiles follows:
|
|
|
|
default/linux/amd64/13.0
|
|
default/linux/amd64/13.0/no-multilib
|
|
hardened/linux/amd64
|
|
hardened/linux/amd64/no-multilib
|
|
|
|
* You can set the GENTOO_PORTAGE_CLEANUP environment variable to true (or
|
|
anything other than False) to clean up portage from the system and get the
|
|
image size smaller.
|