> I would argue that there is another case that is not as rare;
> dependencies. If a user tries to install my module via CPAN I would like
>  it to be able to determine what other things need to be tracked down.
> And these dependencies may be different depending on the target mod_perl
> API version.

ah, nice idea :)

 >>it also assumes that your mp1 user will actually have A-T installed.   next
>>time we get together I'll need to rant a bit about how I can't stand modules
>>that refuse to _build_ because my @INC lack things they need only for their
>>_test_ environment.
> 
> 
> Oh, I completely agree. I like M::B's idea of 'build_requires' and it
> would be nice if it also had a 'test_requires' as well.

:)

>>dialogue saying something like
>>
>>  this module can be installed for either mod_perl 1.0 or mod_perl 2.0
>>  but you need to choose now: [1/2]
>>
>>and then leave you do do what you require.
> 
> 
> Ooohhh, that would be nice :)

yeah, I think that's really the best route, but the implementation really
depends on who has the free tuits atm to make something work.

in the meanwhile, a well documented

  $ perl Makefile.PL MP2=1

in your personal INSTALL file might suffice.  that's probably the route I
would go myself if I wanted to launch something right now.


>>mp1-only modules or modules that require no build-time interaction could
>>simply forget about querying all together.
>>
>>anyway, IIRC dorian has done some work on this front.  probably not like
>>what I've just described, but he's done _something_ which is a start :)
> 
> 
> I don't have a lot of time right now to help, but if he has any ideas or
> something that partially works, I'd be willing to be a sounding/testing
> board.

yes, me too.  I have Apache::Template ported to mp2 and if there were a
universal solution that's at least another module that would test/adopt it.
 but my free tuits are rare these days wrt actually implementing it.

>>of course, there's nothing preventing you from using Apache::TestConfigData
>>etc now yourself.  however, I don't think that is a viable or wise long-term
>>solution to the issue at hand.
> 
> 
> I think you convinced me of how bad an idea this is, so I turn my head
> and walk the other way :)

:)

--Geoff

Reply via email to