To support the dynamic pci hotplug in guest ppc64-diag and its dependency packages are needed, it would be good to have it provided in default iso image and it would be good to have them installed by default. We do have ppc64-diag package in fedora .. I would think we can include this in the base installation ..
A change like this to the Core comps group (https://pagure.io/fedora-comps) is needed diff --git a/comps-f27.xml.in b/comps-f27.xml.in index db2c85a..1e9671d 100644 --- a/comps-f27.xml.in +++ b/comps-f27.xml.in @@ -719,6 +719,7 @@ <packagereq type="default">dracut-config-rescue</packagereq> <packagereq type="default">firewalld</packagereq> <packagereq type="default">NetworkManager</packagereq> + <packagereq type="default">ppc64-diag</packagereq> <packagereq type="default">ppc64-utils</packagereq> <packagereq type="optional">dracut-config-generic</packagereq> <packagereq type="optional">initial-setup</packagereq> The question is whether type should be "default" (user can de-select in installer gui) or "mandatory" (always installed).
No, this isn't the way to do this. It's already handled in the lorax templates that generate the installer isos
> + <packagereq type="default">ppc64-diag</packagereq> > <packagereq type="default">ppc64-utils</packagereq> See this: https://github.com/rhinstaller/lorax/blob/master/share/templates.d/99-generic/runtime-install.tmpl#L53
The lorax template controls what goes into the installer ISO, but not the system being installed. I guess we need both.
(In reply to Dan Horák from comment #5) > The lorax template controls what goes into the installer ISO, but not the > system being installed. I guess we need both. I think for arch dependent installs there's actually somewhere in anaconda/pykickstart/server profile that's better for it. I'll check
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
PR for comps: https://pagure.io/fedora-comps/pull-request/111 PR for lorax: https://github.com/rhinstaller/lorax/pull/204