On Mon, 14 Jul 2003, Stas Bekman wrote: [ ... ] > Are you talking about the dependencies list? by 'the current > state of affairs with mod_perl 2.0', you mean that it's not > indexed by PAUSE. It's available from CPAN. > > Actually, once it gets indexed by CPAN it'll break all the > other modules which specify mod_perl (1.0) as a dependency and > won't work with 2.0.
Perhaps it might be an idea, at this stage, to recommend to module authors that, if their package is for mod_perl 1 only, to use a module like Apache::Constants in their PREREQ_PM (ie, something available only within mod_perl 1), and if it's for mod_perl 2 only, use something like Apache::Const, or something available only with mod_perl 2. This won't help existing packages, but it would at least alert people that a problem is on the horizon. To help in this, perhaps it would be worthwhile to promote the use of Module::Install? A package (Module::Install::mod_perl?) could be made which would make available a function to test for the mod_perl version a user has, and then decide if this is appropriate for the package about to be installed. If the required mod_perl version isn't present, one could either offer to add the required version to PREREQ_PM, or else just die, as automated installs of mod_perl can be tricky. A lot of the code for this could be extracted from Apache::Test; Stas, you've also worked through this logic in making packages that include different versions for different mod_perl versions. Only the package author need have Module::Install::* when constructing the Makefile.PL - the necessary stuff for the added functionality is added to the distribution, making it transparent to the user. -- best regards, randy kobes
