On Wed, 30 Jun 2004, Stas Bekman wrote: > Randy Kobes wrote: > > It was discussed earlier about renaming the aprext static > > library (used to build APR::* outside of mod_perl.so) to > > modperl_aprext, and then install it in the Apache2 lib/ > > directory, so as to be available to 3rd party modules. The > > following diff does that. I've created an aprext_libs sub > > within Apache::Build to return the name of the library (in > > analogy with the apache_libs and modperl_libs subs); this is > > more as a placeholder for the future, when subclasses > > containing platform-specific code for Win32 are made. > > +1 > > I'm not 100% sure about the naming though. If this is for > third party modules which need that library w/o mod_perl, > then won't it be confusing if they have to use something > that includes mod_perl in the name? Won't they start > asking questions, do I use mod_perl?
That's a good point ... I suggested modperl_aprext so that it's apparent where it came from, but that name can be confusing in the sense you suggest. > Granted, you can't have APR w/o building mod_perl, but > it's possible to have APR w/o mod_perl if someone creates > binary packages which provide only the files needed for > APR, in which case modperl_ might be not the best name. > May be we need to come up with aprperl_ or perlapr_ or > perl_apr_ (or else) prefix for methods and for filenames > which don't need modperl? I was thinking along those lines too in making up a ppm package for apreq2 - on Win32, all one needs is the APR/APR::* modules, so in principle one could make up a self-contained apreq2 package that doesn't need mod_perl installed. From a maintenance point of view that might be a mess, but it does illustrate your point - the modperl_ prefix might be confusing in a context outside of mod_perl. So I'll hold off until a better name is decided upon. It's a bit tricky, as the method names also have to make sense within the context of mod_perl, where they might not have a direct connection to apr ... Perhaps something with "common" in the name, as most of these come from a modperl_common_* file? -- best regards, randy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
