0131d7fbf1
Unfortunately, rsync returns exit code 23 (Partial transfer due to error) if it cannot write extended attributes (with -X) because the target file system does not support it, e.g., the FAT EFI system partition. We need -X because distributions using file system capabilities and/or SELinux require the extended attributes. But distributions using SELinux may also have SELinux labels set on files under /boot/efi, and rsync complains about those. The only clean way would be to split the rsync into one with -X and --exclude /boot/efi and a separate one without -X for /boot/efi, but only if /boot/efi is actually an EFI system partition. For now, this hack will have to do. See also: https://bugzilla.redhat.com/show_bug.cgi?id=868755#c50 for the same issue in Anaconda, which uses a similar workaround. |
||
|---|---|---|
| .. | ||
| bootloader | ||
| displaymanager | ||
| dracut | ||
| dracutlukscfg | ||
| dummycpp | ||
| dummyprocess | ||
| dummypython | ||
| finished | ||
| fstab | ||
| grubcfg | ||
| hwclock | ||
| initcpio | ||
| initcpiocfg | ||
| initramfs | ||
| initramfscfg | ||
| interactiveterminal | ||
| keyboard | ||
| license | ||
| locale | ||
| localecfg | ||
| luksbootkeyfile | ||
| luksopenswaphookcfg | ||
| machineid | ||
| mount | ||
| netinstall | ||
| networkcfg | ||
| packages | ||
| partition | ||
| plymouthcfg | ||
| removeuser | ||
| services | ||
| summary | ||
| umount | ||
| unpackfs | ||
| users | ||
| webview | ||
| welcome | ||
| CMakeLists.txt | ||
| globalStorage.yaml | ||
| README.md | ||
| testmodule.py | ||
Calamares modules
Calamares modules are plugins that provide features like installer pages, batch jobs, etc. Each Calamares module lives in its own directory.
All modules are installed in $DESTDIR/lib/calamares/modules.
Module directory and descriptor
A Calamares module must have a module descriptor file, named module.desc, this file must be placed in the module's
directory.
The module descriptor file is a YAML 1.2 document which defines the module's name, type, interface and possibly other
properties. The name of the module as defined in module.desc must be the same as the name of the module's directory.
There are two types of Calamares module:
- viewmodule,
- jobmodule.
There are three interfaces for Calamares modules:
- qtplugin,
- python,
- process.
Module-specific configuration
A Calamares module may read a module configuration file, named <modulename>.conf. If such a file is present in the
module's directory, it is shipped as a default configuration file.
The module configuration file, if it exists, is a YAML 1.2 document which contains a YAML map of anything.
All default module configuration files are installed in $DESTDIR/share/calamares/modules but can be overridden by
files with the same name placed manually (or by the packager) in /etc/calamares/modules.
Qt plugin viewmodules
Currently the only way to write a module which exposes one or more installer pages (viewmodule) is through a Qt plugin.
Viewmodules should implement Calamares::ViewStep. They can also implement Calamares::Job to provide jobs.
To add a Qt plugin module, put it in a subdirectory and make sure it has a module.desc and a CMakeLists.txt with a
calamares_add_plugin call. It will be picked up automatically by our CMake magic.
Python and process jobmodules
Batch jobs for Calamares can be written as Python scripts or as generic commands (shell scripts, external programs, etc.).
To add a Python or process jobmodule, put it in a subdirectory and make sure it has a module.desc.
It will be picked up automatically by our CMake magic.
CMakeLists.txt is not used for Python and process jobmodules.
A Python jobmodule is a Python program which imports libcalamares and has a function run() as entry point.
run() must return None if everything went well, or a tuple (str,str) with an error message and description if
something went wrong.
Calamares offers a Python API for module developers, the core Calamares functionality is exposed as libcalamares.job
for job data, libcalamares.globalstorage for shared data and libcalamares.utils for generic utility functions.
Documentation is inline.
All code in Python job modules must obey PEP8, the only exception are libcalamares.globalstorage keys, which should
always be camelCaseWithLowerCaseInitial.
For testing and debugging we provide the testmodule.py script which fakes a limited Calamares Python environment for
running a single jobmodule.