On Wed, Oct 22, 2003 at 12:17:52PM -0700, Stas Bekman wrote: > > So if my module requires at least mod_perl 1.26 but won't work with 2.0, I > should be able to pass in PREREQ_PM: > > mod_perl => [ 1.27, 2.0 ],
> Do you think this is hard to implement? I've no idea, but it ought not to be. > I've been trying to come up with solutions for a long time. I don't think > it's a problem of tuits to do the actual implementation. I have suggested > to fund a project to resolve those problem. But before it can be funded it > needs to be spec'ed out. But I keep on getting 'not in the near future' and > similar answers :( Last time, this issue was discussed at p5p meeting in > Paris, it was decided that it'll be resolved at the CPAN meeting in Oct. > But it wasn't. That's a pity. > I wish it was something that was a bother only to me personally. I can go > to CPAN and manually get what I want. The problem is that it's a big bother > with a huge community of mod_perl users. And all complaints end up on the > mod_perl developer's table. And the ball hasn't even started to roll yet. > It will soon. It's not going to be pretty. I agree that this is something that needs to be addressed urgently. Sadly I have zero time to help, beyond the odd email here. I'd suggest that you look into implementing the PREREQ_PM change you've outlined. If it turns out to ne non-trivial ask for more help. There were quite a few people willing to contribute in various ways at the meeting. This is a significant issue for the community and so I'd hope someone would offer to help. The relative silence here is troubling. Perhaps it's the wrong list and/or we're the only people subscribed :( Tim.
