Package Manager OEL5R3 not working like it does in RHEL5R3

Question

In Red Hat after you register with RHN, the Package Manager (Add/Remove Programs in the menu) will show a list of package groups that can be pulled from the installation media on the Browse tab. I have found this to be very helpful during initial setup of a system and it does not seem to work at all with OEL5R3.
I have been able to populate the List tab by setting up a yum repository, but was really hoping to see the package groups (which contain many pre-selected packages) in this tool.
I have done a lot of searching and there seems to be very limited information about this tool. When attempting to view the setup on a RHL box through the GUI the app dumps with a python error. The config files themselves do not appear to be straight up yum config files.
Anyone have this working? Does it work properly on R1 or R2?
Thank you...
-Andy

Answer 1

Time for me to clarify, again :)
1) RPM package groups are a supported feature for OEL, including the RPM tools.
2) The availability of package groups, along with their presentation offering
on the pirut, system-config-packages, or GNOME menu, depends on whether or
not a particular repository provides the necessary "comps.xml" definition
files. Without these files, pirut doesn't know anything about package
groups.
3) OEL installation media provides these "comps.xml" files, so RPM package
groups are available during initial installation.
4) The ULN Network has the files available for download, depending on the
channel subscriptions, but does not utilize them for the ability to download
or update on a package group basis.
5) Oracle offers a public YUM repository, where package groups may be used.
More details on this are on the http://public-yum.oracle.com web site,
including a "public-yum-{el4,el5,ovm2}.repo" definition file that can be
installed into "/etc/yum.repos.d/" for yum(8) access.
6) Once you have the public YUM repository setup from #5, you can use pirut,
system-config-packages, et. al., to install an RPM package group.
The catch is the packages will be from the original distribution media, so
after that you must "yum update" or "up2date --update" to get the latest
versions.
Hope this clarifies my earlier too-succinct response.