Bug 575742
Summary: | RFE: %packages section to be able to include a flat file package list | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jasper O'neal Hartline <Jasper.Hartline> |
Component: | pykickstart | Assignee: | Chris Lumens <clumens> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | clumens |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-23 14:17:38 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jasper O'neal Hartline
2010-03-22 10:14:55 UTC
I also forgot to mention that allowing this construct, will ease modularity with kickstart files when the package list to include may be huge. This makes it much easier to administrate and segregate pieces of kickstart installs which could in turn make things more flexible with what package set is to be included. I'd much rather for example have 5 flat files with specifications for different packages, than to have 5 seperate kickstart files when the only thing that will differ in the whole kickstart process is the package set. I know the Fedora Project produces nightly builds and I cannot say for sure they even use the %packages section to specify which packages are to be installed, but even if they did I believe they would let the comps take care of ti since it is an official nightly LiveCD build, meaning they can simply do @base and @gnome-desktop or @games Rather than having huge kickstart files, unfortunately this doesn't work for the general public when wanting to specify particular package sets, and only those packages directly, without specifying the group. Like using %packages --nodefault fluxbox openbox gnome-session gnome-panel @thisgroup This just makes package selection in kickstart situation this much more modular, flexible and fine grained. (Assumed the package file list can also specify what NOT to install if it wants) Like: (package.list): -fluxbox openbox -NetworkManager gnome-panel Maybe this does or doesn't make sense to allow, please advise. kickstart already has a %include directive that's briefly documented at https://fedoraproject.org/wiki/Anaconda/Kickstart. This can be used within the %packages section. Is that what you're looking for? Yes, that is exactly what I was looking for. Ok I looked and for some reason did not come across this. Interesting, ok thanks. Works as I expected. Thanks a lot. |