Managing Internal Yum Repository Groups
        Posted  
        
            by 
                elmt
            
        on Server Fault
        
        See other posts from Server Fault
        
            or by elmt
        
        
        
        Published on 2011-01-10T21:34:58Z
        Indexed on 
            2011/01/10
            21:55 UTC
        
        
        Read the original article
        Hit count: 306
        
What is the best method for handling yum groups dependencies?
For example, take this comps.xml file
<comps>
  <group>
    <id>production</id>
    <name>Production</name>
    <default>true</default>
    <description>Packages required to run</description>
    <uservisible>true</uservisible>
    <packagelist>
      <packagereq type="default">ssh</packagereq>
    </packagelist>
  </group>
  <group>
    <id>development</id>
    <name>Development</name>
    <default>false</default>
    <description>Packages required to develop</description>
    <uservisible>true</uservisible>
    <packagelist>
      <packagereq type="default">gcc</packagereq>
    </packagelist>
  </group>
</comps>
which is packaged with createrepo -g comps.xml x86_64.
The ssh and gcc rpms are not installed in the x86_64 directory.
If I run yum groupinstall development, yum is smart enough to pull the gcc package from the RHEL repo even though the groups are defined in my internal repository. However, is this the proper way of doing this, or should I copy the rpms to my local repository and recreate the repo?
© Server Fault or respective owner