Ayhan Ulusoy wrote: [...]
Bundle::ModPerl2 or something like that could do the trick.
It's there and called Bundle::Apache2 (just like mp1 has Bundle::Apache). It's not exposed on CPAN yet, becase currently mp2 is not indexed by PAUSE.
[...]
MP2 has, to a certain extent, resolved this with the "ModPerl::" and "APR::" namespaces. Thanks a bunch for that.
It's Doug who you should thank ;)
[...]
If you don't like ModPerl::, Apache:: could be OK too.
In particular case of VMonitor, which is really an application and the user shouldn't care what kind of handler it is, I'd put it in (Apache|ModPerl)App:: namespace or something like that.
[...]
Your analysis and proposal are both very good. If you are willing to lead the process, I'm game to change my modules to comply. You probably want to run and polish the namespaces idea through the modperl list.
Per Einar Ellefsen has started the standardisation effort some time ago: http://perl.apache.org/products/apache-modules.html
That's examctly the problem, as CPAN (and PAUSE) have no notion of supporting several branches/generations of the module. Unless you ask for a specific version number, it'll always fetch the latest one. That's the issue I'm trying to resolve with CPAN folks. Once mp2 is released we are going to have a lot of complaints of people trying to install mp1 and getting mp2 instead
Looks like we aren't going to get anything changed on this plane any time soon ;(
As you said : implementation details don't matter : You can perfectly have mp1 and mp2 packaged together and let MakeMaker (or the other thing you're using) decide... ;)>
Just kidding. But I think it demonstrates how messy these dependency issues can get. And sometimes (but not always), it might just be better changing the name.
For "mod_perl.so", I really don't see any clean way, apart from CPAN handling intricate dependency checks with a min _and_ max version, or some kind of 'flavor' category as you say. Or maybe p5p will accept to put the httpd flavor into the architecture string. Hmmm, isn't that an idea;) Either way, it seems quite messy. Good luck ;)
For API modules, why not use the Apache2 trick, or something similar throughout.
We already do that. If you use ModPerl::MM::WriteMakefile with your mp2 3rd party modules (and you need to use that instead of EU::MM::) it does that trick without you moving a finger.
I thought that was quite clever of you guys. In a way, it boils down to the architecture-dependent thingy, but is implemented by mod_perl instead of Perl itself.
Thank Doug again ;) There is a module called 'only' which does the arch-trick for any module.
For handler modules, why not use the scheme above.
FWIW, it doesn't solve the versioning problem. Once you hit mp3, you again will have this problem. Will you rename modules again?
Just jotting down ideas here.
Please keep those coming.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
