On Wednesday 24 October 2001 20:05, modperl wrote: > I would think this would be our problem. How bad is it going to look when > an installed userbase gets shutdown due to a module that was changed just > enough to break functionality in the modules.
I didn't want to imply that we shouldn't check our modules, and the associated versions. In fact, we should probably use strict versions (as un Bundles) to avoid that problem. Simply that we can't quality ensure CPAN as a whole (and others are already working on that). > P5EE(I thought Perl Enterprise > Architecture sounded a bit bigger and better) I agree. I suggest we come back to finding a better name in the few minutes before we start coding. > This doesn't resolve the issue of having users who upgrade packages on > their own though. Documentation: P5EE relies on modules foo, bar, and baz. If you upgrade them separately from P5EE, you're looking for trouble. We could also have a separate installdir that would get use lib'd (so to say) when one does use P5EE; -- _______________________________________________________________________ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com ----------------------------------------------------------------------- "What I like about deadlines is the lovely whooshing sound they make as they rush past." --Douglas Adams
