On Sat, 1 Feb 2003, Stas Bekman wrote: > I've UNINST=1 set in my CPAN/Config.pm, so that older versions > will be automatically cleaned up. Now that means if I install > mod_perl 2.0 or any 3rd party 2.0 modules, the 1.0 version will > get uninstalled. In case of mod_perl 1.0, it'll be uninstalled > only partially (since it uninstalls only the same filenames > that it's installing). > > Another problem with CPAN is that it would be impossible to > upgrade 1.0 modules, if the corresponding 2.0 versions will be > on CPAN :(
I'm not sure about this problem for mod_perl itself, but perhaps one way to address the problem of 3rd party modules (with both mod_perl 1 and 2 versions) is for authors to distribute the modules in the same distribution and then adopt a convention to arrange for the mod_perl 2.0 modules to be placed under Apache2/. The user can then (interactively) install either one (or both) versions without affecting the other (I'm not sure about this for modules with xs components, though). However, for CPAN.pm, 'use Apache2' wouldn't normally be done so as to adjust @INC to see the installed Apache2 modules. Perhaps PERL5LIB would have to be set by the user, which isn't great - if it was a simple thing, perhaps Andreas might include such a functionality in CPAN.pm. Another thing, as you mentioned, is the version numbering used by CPAN.pm to recommend upgrades. Assuming the module name is the same for both mod_perl 1 and 2 versions, what might work, if the author has both versions in the same package, is for the mod_perl 1 and 2 version numbers to be synched when an update is made. -- best regards, randy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
