On Sun, 2003-10-26 at 17:50, Robert G. Brown wrote:
> I'm about half way through writing a perl script to create a list of
> groups and packages that would recreate an existing install in either
> kickstart or via yum, and I encounter my own ignorance. To help me
> avoid RTFM, I entreat the following Enlightenment.
>
> When running yum -y -d 0 grouplist hidden groupname, one gets a results
> such as:
>
from the top of yumcomps.py:
# goals
# be able to list which groups a user has installed based on whether or
# not mandatory pkgs are installed and whether all the metapkgs are installed
# (consider making metapkgs groups with settings in this model)
# so groups have end up being default, optional or mandatory
# - all groups (as listed in the xml file are default only)
# so installgroup X installs all the default+mandatory pkgs and any group
# determine if groupreqs are included on install
# is installed? - group reqs not consulted - metapkgs and pkgs in mandatory
# install - groupreqs installed too - metapkgs in default or better
# and pkgs in default or better
# update - if pkg in group installed (any class of pkg) check for update,
# all mandatory pkgs and metapkgs will be updated/installed if possible
# ???? Ask - should update recurse the pkg group list so you could run
# yum groupupdate "Workstation Common"
# erase - only pkgs in group - not subgroups nor metapkgs
#
# gist of operation of this class:
# create the class
# add comps.xml type files
# compile the groups
# then you can perform the functions on the groups
# which groups are around.
# maybe parse the files, populate the fields as much as possible then sweep
# through and calculate things after all the .xml files have been added
# need to deal with groupname vs groupid
does that help? If not - go check out info on comps.xml - that should
explain the grouping/package options.
-sv
