> OK, here's a situation. One of the programmers at your company runs the
>disk out of space. You're going to go bonk him on the head, but first,
>there are more pressing matters. PostgreSQL 6.5 has horked up the tables,
>and needs to be fixed. 7.0 is released, which has a fix for the problem.
Let's be real here. If your system is out of disk space, you can't do a dump
to put it into 7.0. You're definitely gonna need 6.5 to work at this
point...
> Are you going to sit around waiting for RPM's, while your tables are all
>horked up, and the programming department is breathing down your neck
>because they can't get work done?
If 7.0 is that important, and there's no RPM's yet (which is a case I
haven't seen happen yet) then you should compile from source, but make the
RPM as you compile. It'll add about 5 minutes to your task, and save you a
world of pain if you have more than one machine to fix.
Your problems aren't with RPM's, your problems the FHS. Distrib packages
(RPM *or* DEB) will put stuff in FHS compliant locations, packages by anyone
else will put files where they want. If you feel that's incorrect,
Irespectfully suggest you hit up the LSB/FHS people if you want that to
change, NOT Red Hat, PostGreSQL, or anyone else.
Rob Nelson
rdnelson@co.centre.pa.us
