| Table of Contents | ||
|---|---|---|
|
...
Notes:
So far, the selinux-*policy RPMs have handled whatever I’ve tried
Ancient policy wiki at https://fedoraproject.org/wiki/SELinuxModularityDesign (probably outdated)
Supporting questions
Can we repackage a “thinned-out” module with only select packages?
probably:
EL8 RPM prereqs: createrepo_c (appstream) + modulemd-tools (epel)
Process:
Code Block # Create initial repo with ursine modules mkdir -p $NEW_REPO_DIR/Packages/ursine cp "${URSINE_PACKAGE_FILES[@]}" "$NEW_REPO_DIR/Packages/ursine/" cd "$NEW_REPO_DIR" createrepo_c .
Modularity CLI examples
Simple dnf module commands
...
| Info |
|---|
This is one of the few (two?) module commands that lists the Repo that provides reports which DNF Repo hosts the module |
View the packages in each profile (for a specific stream)
...
| Info |
|---|
Judging by the bug report at https://bugzilla.redhat.com/show_bug.cgi?id=1547041, The current behavior only resolves module packages using default or enabled streams & profiles. |
Clean DNF install --downloadonly with all deps, without needing mock
Make sure you enable/disable the repos to match what you intend for resolution; --config is an option, too.
| Code Block | ||
|---|---|---|
| ||
DNF_DLONLY_TARGET_PACKAGE=httpd
DNF_DLONLY_INSTALL_ROOT=/root/fake-install-dir
DNF_DLONLY_PACKAGE_DIR=/root/downloadonly
dnf install --downloadonly \
--installroot="$DNF_DLONLY_INSTALL_ROOT" \
--downloaddir="$DNF_DLONLY_PACKAGE_DIR" \
--enablerepo=appstream \
--disablerepo=test \
--releasever=8 \
"$DNF_DLONLY_TARGET_PACKAGE" |
Documentation
https://sgallagh.wordpress.com/2019/08/14/sausage-factory-modules-fake-it-till-you-make-it/
Notes on building modules independently of Fedora’s hosted build system
https://pagure.io/modularity/issue/141
> * AGREED: Profiles cannot be removed during the lifetime of the stream in order to avoid breaking scripts. Options may exist for exceptional cases on an individual basis. (contyk, 15:41:06)