I'm not too hot on rpm's (nb. rpms=source files) but it would be a good idea if only to detect dependancy conflicts. I wouldn't include gcc or anything else apart from what BRL is itself develops because...
1) gcc and other sw is/should already be installed if user has development in mind
2) If not installed they should be sourced from the user's own distributions packages (hence avoiding a lot of potential dependancy problems)
3) Including the likes of gcc could cause MAJOR problems if it installs but subsequently conflicts with other software
4) gcc is DAMN CRITICAL - don't go near it unless you really have to
5) You would be making a lot more work for yourself in maintaining packages
1) gcc and other sw is/should already be installed if user has development in mind
2) If not installed they should be sourced from the user's own distributions packages (hence avoiding a lot of potential dependancy problems)
3) Including the likes of gcc could cause MAJOR problems if it installs but subsequently conflicts with other software
4) gcc is DAMN CRITICAL - don't go near it unless you really have to
5) You would be making a lot more work for yourself in maintaining packages