Minimal installation - RHEL - Development tools libraries

For the OS installation the cPanel documentation, http://www.cpanel.net/docs/whm/Installation.htm , says:
"A fresh install with minimal installation options is recommended. Development tools libraries (gcc, C, etc) and wget are required. cPanel and WHM will install Apache, MySQL, exim, PHP, etc. You do not need to install any of these services beforehand."

We'd like to follow this and keep the number of rpms installed to the minimum so that the rpm managed packages and the cPanel managed packages don't interfere with each other. Now, what are the rpms necessary for the "Development tools libraries (gcc, C, etc)"? Are the following enough:

gcc

glibc-devel

gcc-c++

libstdc++-devel

Anything else? Do you need the Perl rpm? Is there a meta-package of the required "Development tools libraries (gcc, C, etc)"?

make sure you install yum ; so that as and when the cpanel install proceeds; it will get its own required rpms in case they are missing.

Click to expand...

Thanks.
If cPanel installs the Perl rpm, or any other rpm, are we OK to install rpm updates for that package using yum? That is, if cPanel installs an rpm is cPanel going to respectfully use the rpm package management system or is cPanel going to install an rpm and then write over some of the files for that package itself or something similar? Note that the updates to a release of RHEL are only security fixes, bug fixes. and enhancements but keep the application interfaces stable.

cPanel installs the necessary rpms for its installation. however, it cannot be said whether you can go for a direct update, for example, take the case of apache compilation. Apache is compiled against the binaries from the installed rpms as well as libraries and sometimes upgrading without proper check up might result in a broken system.

cPanel installs the necessary rpms for its installation. however, it cannot be said whether you can go for a direct update, for example, take the case of apache compilation. Apache is compiled against the binaries from the installed rpms as well as libraries and sometimes upgrading without proper check up might result in a broken system.

Click to expand...

Thanks for the answer. I was hoping that wasn't the case.

What is considered best practice for keeping a cPanel server up to date? Letting cPanel keep the vast majority of system, including rpms, up to date and only doing manual rpm updates on selected packages that are out of cPanel control, for example, the kernel. Or keeping all the rpms up to date using yum being aware of potential breakage to the system.

Do you have to be careful about installing rpms after a cPanel install?

What is considered best practice for keeping a cPanel server up to date? Letting cPanel keep the vast majority of system, including rpms, up to date and only doing manual rpm updates on selected packages that are out of cPanel control, for example, the kernel. Or keeping all the rpms up to date using yum being aware of potential breakage to the system.

Do you have to be careful about installing rpms after a cPanel install?

Click to expand...

There are some parts that you can set automaticly upgrade or manually. The parts are:
mysql, courier, system packages, Cpanel upgrade, python and ftp.

Only apache/php and kernel upgrade is manually.

All of the important rpms are coming directly from Cpanel and not from package system of the installed distro.