Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <4231A01C.2020608@modperlcookbook.org>
Date: Fri, 11 Mar 2005 08:41:48 -0500
From: Geoffrey Young <geoff@modperlcookbook.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040927
MIME-Version: 1.0
To: Joe Schaefer <joe+gmane@sunstarsys.com>
CC: dev@perl.apache.org
Subject: Re: CGI.pm dependency in Apache2::Status
References: <20050308015855.29523.qmail@minotaur.apache.org>
 <422D0919.8040406@modperlcookbook.org>
 <87sm35oanz.fsf_-_@gemini.sunstarsys.com>
In-Reply-To: <87sm35oanz.fsf_-_@gemini.sunstarsys.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


> This is something we will need to deal with.  Once we
> can get a fixed CGI.pm on CPAN, I think we should list 
> that as a prereq for mp2.

ok, I've been looking at how to fix this and I'm not sure I have the answer.

CGI.pm says this currently:

  if (exists $ENV{MOD_PERL}) {
    eval "require mod_perl";
    if (defined $mod_perl::VERSION) {
      if ($mod_perl::VERSION >= 1.99) {
        $MOD_PERL = 2;
        require Apache::Response;
        require Apache::RequestRec;
        require Apache::RequestUtil;
        require APR::Pool;
      } else {
        $MOD_PERL = 1;
        require Apache;
      }
    }
  }

now, I was going to change this to

    eval "require mod_perl";
    eval "require mod_perl2";
    if (defined $mod_perl::VERSION) {
      if ($mod_perl::VERSION >= 1.99) {
         require Apache::Response;
         ...
      }
      elsif ($mod_perl2::VERSION) {
         require Apache2::Response;
         ...
      } else {
         ...
      }

but I'm not so sure I like it - it means that we can potentially be juggling
around 3 different mod_perl versions within the same site_lib, which is just
doomed.

but, that approach will work just fine if mod_perl refuses to install over
an existing mod_perl.pm, either mp1 or prior mp2 releases...

we are, of course, going to have a _huge_ migration effort on our hands once
the current path is released - people with Apache::Response and
Apache2::Response both in site_lib and their "porting" goes just fine until
they move to a new box and see they missed Apache2:: renames all over the
place.  all in all, this strikes me as having a larger backlash in the
community than started all of this.

so, I'm increasingly of the opinion that we should refuse to install
mod_perl 2.0 over any other existing mod_perl installation.  make them start
from a new perl tree, remove the old tree, or whatever.  just minimize our
mailing list burden by doing this up front.

thoughts?

--Geoff

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org