Description of problem: if PostgreSQL Database group is selected in anaconda during an install neither the server or client are actually installed. just support and perl/python libs. this is counterintuitive to the end user. automatic inclusion of the server/client when the group is selected, as is the case in fedora comps.xml, would seem to meet the expectation of the customer better. Version-Release number of selected component (if applicable): RHEL3 and RHEL4 How reproducible: customize installation of RHEL and choose PostgreSQL Database group in anaconda after installation open a term and try to execute psql. result will be the command not found. Steps to Reproduce: 1.install RHEL 2.customize packages during install 3.choose PostgreSQL Database group Actual results: attempt to execute psql will fail due to the program not being installed Expected results: execution of psql Additional info: within the comps files for RHEL the server component is optional while in the fedora comps the server is manditory the fedora inclusion of the server component is consistent with the expectation that when a the user selects to install PostgreSQL that the server (and client) will actually be installed. Secondarily, installation of the support libraries for perl/python, which is manditory in RHEL, would seem to be more applicable to selection of the Development group. But this is less important than the server/client aspect. i would recommend that the comps file be modified to follow the fedora example of inclusion of the server as manditory when the group is selected.
This is not being changed at this point for RHEL 4.