my feeling is that by the time we are ready for an official 2.0 release, 2.0.46 will be sufficiently old that it is a reasonable point of support. personally, I'd like to use 2.0.47 and remove all back-compat code, but since 2.0.46 is the same version required by libapreq, I thought that was a compelling reason to not use 2.0.47.
IIRC the reason we needed 2.0.46 in apreq was apxs- our current
build system relies on apr/apu path info coming from apxs, and it wasn't until 2.0.46 that apxs supplied it (correctly). If there's
a compelling reason to prefer 2.0.47 for modperl (like dropping the back-compat code for apr), I say go for it.
well, right now if we used 2.0.47 we would have no back compat code (for the moment, anyway :). supporting 2.0.46 means back compat for at least one function.
however, until apr reaches 1.0 I expect we will always have some level of back compat to worry about. so, either 2.0.46 or 2.0.47 is fine with me, and we can revisit the idea when apr reaches its freezing point. I still like the idea of maintaining (but not enforcing) a parallel with libapreq though, since the two are closely related from a user perspective.
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
