Re: [summary] The Conflict of mp1 vs mp2 vs mp22 vs ... vs mpNN

[prev] [thread] [next] [Date index for 2004/12/31]

Joe Schaefer wrote:
> Stas Bekman <stas@xxxxxx.xxx> writes:
> 
> 
>>Joe Schaefer wrote:
> 
> 
> [...]
> 
> 
>>>Looks very promising to me.  Is there a way to tell PAUSE to index
>>>mod_perl's Apache::* modules from a bundle?  If so, that might
>>>provide a decent solution for both mod_perl and libapreq
>>>(and other Apache::* modules that find themselves in a similar situation).
>>
>>I'm not sure I understand what you ask, Joe. The indexer indexes
>>anything that upload to PAUSE (as long as you have perms).
>>
>>So we need release mp1 with a new package:
>>
>>   Bundle::mod_perl1::core
>>
>>which has the same version as mod_perl.pm
>>
>>and mp2 distro with:
>>
>>   Bundle::mod_perl2.0::core
>>
>>which has the same version as mod_perl.pm
>>
>>Now other packages can create a dependency on those packages, instead of
>>mod_perl.pm.
> 
> 
> If you're going that route, 

Not really, I'm just discussing possible workaround.

> I really see that as being 
> worse than introducing a new mod_perl2 package with mp2
> and restoring all of mp1's CPAN indexing (including mod_perl.pm).

But we don't want to rename the API. mod_perl.pm is a part of the API.

> I now think was a mistake for any of the Apache::* core modules 
> to be indexed with mp1, because it looks like a wedding between
> the Apache:: APIs and the mp1 implementation of them.  This is, 
> IMO, the kernel of the complaints against the mp2 release plan.

It has nothing to do with indexing of mp1 Apache::* core modules. When 
Randal has it's finger glued to the 'r' button, CPAN shell checks what are 
the *installed* modules and compares their version against the index. So 
if mp1 didn't index any of those, but mp2 did, you will still have a 
problem. Perhaps you were suggesting that none of the Apache::* core 
modules, but mod_perl.pm, should be indexed (both mp1 and mp2), in which 
case it makes sense.

You still have a problem with mod_perl.pm.

It's easy to fix, one could re-index anything w/o re-uploading the distro.

One could argue that a user may create a dependency on a specific module 
in the core, because they don't care what modperl version is supplied, as 
long as that module has the right version, in which case they will have a 
problem, if core modules won't be indexed. Of course they could go and 
figure out what was the mp version when their prerequisite was first 
satisfied and ask for that mp version.

But this non-indexing approach doesn't resolve the problem for 3rd party 
modules.


        -- 
        __________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@xxxxxx.xxx 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