Joshua Hoblitt wrote:
On Mon, Dec 27, 2004 at 12:10:47PM -0500, Perrin Harkins wrote:
The real significant issue to address, IMO, has to do with CPAN's
indexing of the Apache:: modules common to both mp1 and mp2 core
distros, because those packages set the underlying apache[12]
architecture.
That's what I'm saying -- don't fix it. Tell people they need to keep two
perl installations if they want to run both. They will almost certainly
need to anyway if they intend to port modules from one to the other
without breaking the current working installation or renaming all of their
own modules.
Has any one considered using only.pm?
http://search.cpan.org/~ingy/only/
Please read:
http://perl.apache.org/docs/2.0/user/porting/porting.html#__pm__so__Files_Collision
I'm just not confident that things like PAUSE and CPAN.pm will change in a
timely fashion, and even if they did I don't see how that would help the
millions of mod_perl installations already out there.
They don't all have to change. mp2 just needs to list a 'fixed' version of
CPAN in it's dependencies...
I like your thinking Joshua :)
--
__________________________________________________________________
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
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
