Stas Bekman wrote:
First of all this is a more generic problem than in my particular case, we already have this problem with all packages living in the core and separately on the CPAN. The indexer introduces a special case for perl core.
Ken Williams wrote:
For what it's worth, my solution to that problem would essentially be the same as what I recommended in your case: for core modules that are in CPAN independently, the core should essentially "depend" on the CPAN versions.
Stas Bekman replied:
But it doesn't. Since we want the core to include all the essential modules in the core. If downloading the dependant modules was a trivial thing, the core would simply include them, right?
Nick Tonkin followed up:
But the "core" does not in reality contain all the modules even an end user would need in their environment. I'm thinking specifically of Apache::Request but I'm sure there are others that almost everyone winds up installing.
But I'm not talking about end-user modules at all. Apache::Test and ModPerl::MMUtil are used only during the build and testing of the core mod_perl and 3rd party ModPerl::/Apache:: modules. All I'm trying to do is to minimize the effort of installing/testing things both for users and developers.
What you are talking about is the responsibility of Bundle::Apache and Bundle::Apache2. And indeed Bundle::Apache includes Apache::Request, so whenever you get a new perl install do:
perl -MCPAN -e install Bundle::Apache
and you get all the essential mp1 modules installed.
Nick Tonkin then wrote:
What would be cool would be if there were a great CPAN install bundle for mod_perl that installed dependencies in the regular way and also made the configuration/build process a little easier for the end user. Or even a third party solution ... seems to me there's a tool for building and installing apache and its modules; did you ever check out how it did with mod_perl, Stas? (I doubt it's mp2 compatible for sure anyway). I live on FreeBSD so I'm spoiled, I guess, but I really think mod_perl could benefit from having a more hands-off build process, one that in the process would eliminate this problem you are facing.
Nick, you perfectly know that the phrase 'what would be cool' doesn't work in the open source world, unless it triggers someone's interest, or you yourself make it into a code...
I'm working on a module that will help developers to make their Makefile.PL's simpler, I'm seeking comments on the dev modperl list, in the thread I've started.
And no, I haven't looked at the package you are talking about.
__________________________________________________________________ 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]
