Managing Internal Yum Repository Groups
- by elmt
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?
