Bug 15300
| Summary: | RFE: comps: way to include classes before they are defined | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Pekka Savola <pekkas> |
| Component: | anaconda | Assignee: | Michael Fulbright <msf> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 7.0 | CC: | katzj |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-07-17 15:53:40 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: | |||
Not for 7.0 :) We're going to rethink the comps file. We've made some changes to the comp file format that should address this issue. The new comps file format does allow control of the order that package groups
appear.
<grouphierarchy>
<category name="Desktops">
<subcategory>base-x</subcategory>
<subcategory>gnome-desktop</subcategory>
<subcategory>kde-desktop</subcategory>
</category>
<category name="Applications">
<subcategory>editors</subcategory>
...
CLOSING->RAWHIDE
Time tracking values updated |
As it is, you have to define the comps file classes _before_ you use them. The algorithm should be expanded so that you could also define them later in the file. The reason: the order classes are defined in comps file defines the order they're shown in the installer. If the algorithm were to be reworked you could do something like: ---- 1 base { ... } 1 Our Server { @ Development @ ... ... } ... 0 Development { ... } ---- Now, you have to define the classes you want in 'Our Server' one by one (if you want it to be the first entry in the installer).