On Tue, Oct 21, 2003 at 12:03:43PM -0700, Stas Bekman wrote: > Tim Bunce wrote: > > > >All I recall was that the dependency metadata needs to be able to > >handle more complex expressions than at present in order to prevent > >incompatible future versions of future modules > > Cool. But are there any concrete plans to implement those more complex > expressions? ;)
I hope so, but I'm not the one to ask. > >And then authors would still have to actually add eg "mod_perl < 2" > >to the dependency list of modules that don't support mod_perl 2. > > Yeah, but how do you tell CPAN/CPANPLUS clients that via the PREREQ_PM list? > > And how do they handle that interactively, when users say: > > cpan> install mod_perl > > ? It's certainly a problem. > >Personally I'd suggest renaming "mod_perl" version 2 to "mod_perl2" > >and so completely duck the issue for now. I doubt it could get fixed > >in time for you. > > If it was only one module, than we could consider that. But there are many, > and renaming them is a bad idea, since users will have to modify their code > and make it conditional, even though those modules haven't changed their > user API. e.g. If you have use Apache::Request in your project, it'll work > exactly the same under mp1 and mp2. why changing the name? the only problem > is how the program (dependency list) or the user (interactive) get to tell > CPAN that they want a specific generation. Ah yes. To be honest, I think the only practical solution that could be implemented in time and be used by most people, is to ship both v1 and v2 versions of the module in each distribution. Tim.
