It has been standard practice with Red Hat as long as I have been using linux (MKLinux DR3 was my first distro - and that was Red Hat 5.1 except with the Mach 3 mikrokernel and ppc binaries) to create a package containing just the stuff the user needs to use the software (binary, config files, documentation) in one package - and to put the headers and stuff in a second package noted "devel".
This allows people who don't want to do development on their system to install far less number of packages and thus save space. A lot of people have no intention of compiling anything on their system, and it is common practice on web servers to not install a compiler so that a cracker can't compile any code on the machine should he get on. in these cases, where for whatever reason the user does not want to do any software compiling, the headers for things like bzip2 etc. really *don't* need to be installed. I agree with the Red Hat model of seperating out the headers. Back when I did some web dev on a little IBM Thinkpad with a small hard drive, I didn't *want* the extra space taken that installing headers would take. On Thu, 2002-11-28 at 16:15, Rikard Bostrom wrote: > Hi, > > The reason the program didn't compile had something to do with > bzip2. If I installed the rpm bzip2-development it worked like > a charm... same thing if I downloaded the bzip2 source code > and compiled that. I think it's stupid that the bzip2-development > package wasn't installed in the first place, as I selected all the > development packages in the install. But bzip2 isn't even listed > there, so I had to install it manually. > > I really don't like RedHat's package tool in 8.0, is there an other tool > out there I can use? > > /dahonk -- Michael A. Peters <[EMAIL PROTECTED]> -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
