Mark Post replied... >>> On 2/3/2009 at 11:27 AM, David Boyes <[email protected]> wrote: > On 2/3/09 11:19 AM, "Mike Walter" <[email protected]> wrote: -snip- > They also "recommend" bypassing dependency > checking to force installation of this package, which strikes me as flat out > wrong. What's the point of a software configuration management system if you > bypass it or allow vendors to bypass it?
Well, that's sort of out of context. The -snip- leaves out my comment, but makes it appear that the text below was mine when it was actually David's reply from Tue, 3 Feb 2009 11:27:31 -0500. Just to clarify my position: long term (beyond a couple months of intensive corrective action) I consider this a gross violation of all that is sacred in terms of reliability, availability, support, and upgradability. Dan Martin replied in part: "Bad Vendor. No biscuit!!!" I think even better: "Bad Vendor. No money - no contract!!!" Hit 'em where it counts, and where the customer would be hit when this design flaw all fall apart: in the bottom line. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Mark Post" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 02/03/2009 10:57 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: Philosophical question... >>> On 2/3/2009 at 11:27 AM, David Boyes <[email protected]> wrote: > On 2/3/09 11:19 AM, "Mike Walter" <[email protected]> wrote: -snip- > They also "recommend" bypassing dependency > checking to force installation of this package, which strikes me as flat out > wrong. What's the point of a software configuration management system if you > bypass it or allow vendors to bypass it? That is flat out wrong, and will likely result in a system that is not supported by the OS vendor. There have been times when I've had to use --nodeps for things, but it was definitely not my first choice, and I won't recommend that to any of my customers unless the engineering group tells me to do so. Even then I wouldn't like it, and would demand that the underlying problem get fixed so that the next update went on clean. When you're the one in control of the software and packaging of it, there's no excuse for leaving that kind of land mine out in the field. Mark Post The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
