Hi, On Thu, 9 Mar 2006, J Sloan wrote:
Eberhard Moenkeberg wrote:
On Thu, 9 Mar 2006, J Sloan wrote:
Many vendors e.g. oracle require apps to be rebuilt or relinked in place, and the build fails due to compiler changes - so telling the poor DBA to "FIX YOUR ERRORS" is most unhelpful I'm afraid - so this is an unacceptable answer for most real world scenarios.
Yes, such cases may happen, and they already have happened. You remember gcc-old in SLES? You remember openmotif-libs-<something-very-old>?
So, next step is:
FIX YOUR ERRORS, or at least SHOW THEM IN DETAIL...
"I need this for an older program" is not enough.
Oracle 10 enterprise manager -
Error logs not available right now, but the DBA had to install an older version of gcc to get it built, as Oracle does not support gcc 4, and their support begins with "you must use gcc version x" (known as gcc-old in SLES)
It's fine to push the envelope with new versions, but there must also be a sane fallback for stable production purposes.
Oracle should be a theme within the SLES line only. And you see, there has been a solution for former cases. But THERE, not HERE. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)