Still work to do to finish the groups from comps.xml Right now I have this kinda working manually using mirrorball code but outside of the actual mirrorball automation framework.
How it is going to work for now. * mirrorball reads comps xml makes a list of groups and a list of packages for each group. Next finds the conary version of the packages and adds it to the xml. The factory will read the groups.xml and use the individual groups-foo.xml to create groups. I plan to dep check them against the platform and build the group without actually including the dep packages relying the assumption that the packages needed will be available. For now the factory also makes a group-packages that contains everything... The idea is to make one repo call to get all the latest then do a find by name against that repo to build the comps groups. What I haven't decided on is a dep closed minimal install looking at the comps.xml there are a few groups that seem very important to a minimal install. It could be as simple as including at least these 2 groups in an install line in the system-model then we would very closely follow the Fedora groups for installs Groups that will probably be needed for a minimal install -- group-core.xml -- group-critical-path-base.xml TODO * wire it all into mirrorball so we can start importing the new packages --Add code to mirrorball automation to build groups --Finish moving factory-managed-groups to use GroupSetRecipe --Sanity check the group architecture with others -- Brett C. Smith [email protected] Sr Software Developer Platform Deployment Technologies (919)531-6635 -- x16635 _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
