Stas Bekman wrote:
Geoff,
So as discussed earlier we need to verify which methods have changed. I think Doug has some tools to do that in util/build. However it could be easier to look up all the deprecated functions, which will also tell their replacements.
I've already coded some of the changes but they weren't commited them. See:
* I think I forgot to fix the Functions.pm here: http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=105037778922141&w=2
* same here:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=102913337222667&w=2
I'm not sure if I started to work on others as well, but I can't find any in the archives.
Hope that this gives you an idea on how to start with the sync.
it does, thanks :)
we really ought to pin down exactly how far back we are going to support httpd/apr. since we're not 2.0 yet, we should probably just pick a version to support going forward. for instance, I'm not sure it makes sense to support 2.0.40 anymore - the back-compat stuff is starting to look ugly and I'd rather have clean code than support for httpd versions that are over a year old.
personally, I'd like to see 1.99_10 require a fairly new version, perhaps even as new as 2.0.47 - with 2.0.48 right around the corner, 2.0.47 is likely to be rather old itself by the time we release 2.0.
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
