2a22901ddd
setup_selinux_file_contexts is now called after the config.sh script. This makes sure that eventual policy related changes done in the optional config.sh are covered by a late setfiles call. In addition setup_selinux_file_contexts is called again at the end of any chroot based script hook. So we assume that any optional script target can change the system in a way that a new setfiles call might be required. It can happen that setfiles is called more often than required but as we cannot know what custom scripts does, it's better to call it more often compared to not often enough. This Fixes bsc#1210604 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| base.py | ||
| image_info.py | ||
| image_resize.py | ||
| result_bundle.py | ||
| result_list.py | ||
| system_build.py | ||
| system_create.py | ||
| system_prepare.py | ||
| system_update.py | ||