Re: The danger of blowing away newer modules.
[email protected] (Michael G Schwern) Tue, 4 Sep 2001 21:47:01 -0400
| Newsgroups | perl.sdk |
|---|---|
| Message-ID | <20010904214701.C13483@blackrider> |
On Tue, Sep 04, 2001 at 06:31:24PM -0700, Stephen Zander wrote: > >>>>> "Michael" == Michael G Schwern <Michael> writes: > Michael> Assuming the bits of the SDK are fairly well tested, and > Michael> that all dependent modules are provided in the SDK, then > Michael> the modules in the SDK, as a whole, should work. If they > Michael> don't work, it's tests should fail. > > SDK includes module Foo. > Module Foo depnds on module Bar with version >= 0.5 so SDK includes Module Bar > User has Module Bar (version 0.75) installed. > Module Bar 0.75 has a bug which causes module Foo to fail horribly. > What does the SDK installer program do? The tests for Foo fail, the install fails and the user sends a bug report. Not a whole lot else one can do. The only other alternative is to overlay the newer version with the old, which is not an option. Do you have something else in mind? If updating SDKs is quick (which is will be once I'm through) they shouldn't fall far behind and this shouldn't be much of a problem. -- Michael G. Schwern <[email protected]> http://www.pobox.com/~schwern/ Perl6 Quality Assurance <[email protected]> Kwalitee Is Job One BOFH excuse #238: You did wha... oh _dear_....