>But we have to deliver the apr.so corresponding to mod_jk.so. Exact and and it's not a big problem, if you use packaging tools like rpm/deb.
mod_jk will depend on libapr rpm or /usr/lib/libapr.so I could produce and place both of them in download dir >Pier is right... That is more easy to link apr staticly to >mod_jk. Having to >deliver 2 files instead 1 will only bring more problems. Are you sure ? If there is bug fix in apr, you'll have to rebuild mod_jk. if you like apr and want it more widely used, you should consider it like zlib. >> Also I think the version that comes with Apache2's >> binary is to be considered the 'reference' - since Apr >> was not released independently, the apache2 package can >> be considered as the 'dependency'. > >We need one mod_jk.so for each version of apache2. Yep, I'll stick with Apache 2.0 release (alpha/beta/GA). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
