On Tue, 13 Jul 2004, Geoffrey Young wrote:

> Stas Bekman wrote:
> > In case you may have missed this patch on the users list, here it is
> > again. It ties $Apache2::VERSION to $mod_perl::VERSION so one can
> > require Apache2 for mp2. If it goes in mp1 should also be patched to do
> > the same.
> >
> > I still want to have PAUSE support multi-generations, but this seems
> > like a cheap workaround for the current dependency problem.
>
> I read through the thread on modperl@ but I still don't
> really grok the issue this patch is trying to solve.  I
> mean, I see that it's nice to have mod_perl.pm and
> Apache(2).pm in sync with the same $VERSION (a good idea),
> but outside of it just being nice, what is this buying us
> again?

In a nutshell, the problem is that the PAUSE/CPAN indices
(which CPAN.pm/CPANPLUS.pm) don't allow for multiple module
versions - if one asks to install Foo.pm, the highest
version of Foo.pm will be used. This will be a problem when
mod_perl 2 is released - assuming the $VERSION of
mod_perl.pm in mod_perl-2 is higher than that in mod_perl-1,
then a user using CPAN.pm/CPANPLUS.pm to install mod_perl
will always get mod_perl 2. This might not be so bad for
mod_perl itself, as probably few people install it
automatically, but it will be a problem with 3rd party
modules requiring mod_perl through a PREREQ_PM -
CPAN/CPANPLUS will think they always want mod_perl 2.

The idea behind Apache.pm/Apache2.pm is that these are,
respectively, unique to mp1/mp2. One can then use one of
these modules, rather than mod_perl.pm, in a PREREQ_PM to
demand a particular mod_perl version. The thing with tying
the $VERSION of Apache/Apache2 to the corresponding
mod_perl.pm of mp1/mp2 is that, currently, mod_perl.pm is
used to denote the distribution version, and so by tying
things in this way, a particular mod_perl version can be
required by requiring a particular version of
Apache/Apache2.

That's not much of a nutshell :)

-- 
best regards,
randy

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to