On Thu, 27 Mar 2003, 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.
> >
> >
> > 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.
>
> 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?
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.
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
--
~~~~~~~~~~~~~~~~~~~~
Nick Tonkin {|8^)>
