Comment Re:I have a suggestion (Score 1) 334
I disagree. There are good reasons to have -devel packages these days, and one of them is still disk space.
Careful usage of disk space is very helpful when you're maintaining a farm of virtual machines on shared storage. If your virtual machine is only going to serve DNS, why force it to have lots of files that it doesn't need, and use up space that would be better allocated to other machines?
You suggested deleting files after installing packages to keep things trimmed down, but doing so defeats the point of using a package manager. If I were going to monkey around with the files after installing the packages, I might as well not use a package manager at all. Another argument against trimming files also comes from the virtual machine farm: files to be trimmed do have to be installed during kickstart, making kickstart slower and requiring the virtual disk to be big enough to store the files just long enough for me to delete them. Since, at least with VMware ESX 2.5 and VMFS 2, it's not trivial to shrink drive images, I'm left with wasted space, not to mention wasted time.
Changing files behind RPM's back actually breaks useful functionality. For example, if a piece of software is giving me trouble, I can ask RPM to verify that it's properly installed, but if I've gone and deliberately removed some of its files, of course it'll look like the package is broken. Aside from that, what happens when I do a system update? I'd have to make package trimming an extra step for myself every time. I manage thousands of Linux boxes as part of my work; if I had to do this sort of package trimming I'd go insane.
-lars
Careful usage of disk space is very helpful when you're maintaining a farm of virtual machines on shared storage. If your virtual machine is only going to serve DNS, why force it to have lots of files that it doesn't need, and use up space that would be better allocated to other machines?
You suggested deleting files after installing packages to keep things trimmed down, but doing so defeats the point of using a package manager. If I were going to monkey around with the files after installing the packages, I might as well not use a package manager at all. Another argument against trimming files also comes from the virtual machine farm: files to be trimmed do have to be installed during kickstart, making kickstart slower and requiring the virtual disk to be big enough to store the files just long enough for me to delete them. Since, at least with VMware ESX 2.5 and VMFS 2, it's not trivial to shrink drive images, I'm left with wasted space, not to mention wasted time.
Changing files behind RPM's back actually breaks useful functionality. For example, if a piece of software is giving me trouble, I can ask RPM to verify that it's properly installed, but if I've gone and deliberately removed some of its files, of course it'll look like the package is broken. Aside from that, what happens when I do a system update? I'd have to make package trimming an extra step for myself every time. I manage thousands of Linux boxes as part of my work; if I had to do this sort of package trimming I'd go insane.
-lars
