On 9/4/2004 11:38 PM, Ken Williams wrote:
On Sep 4, 2004, at 10:21 PM, David Wheeler wrote:
On Sep 4, 2004, at 8:18 PM, Ken Williams wrote:
What you want to do is add the appropriate modules to the 'requires'
list when the user passes the --with-pg flag. That will handle
actually getting the appropriate modules installed. *Noting* for
later reference (during testing & runtime) that they actually *are*
installed and tested is what the 'feature' stuff is for.
So I'm dynamically assigning to the required list, and not using the
feature (except perhaps to copy the list of required modules)? Doesn't
that then contradict the requirements in META.yml (this was something
you brought up before, IIRC)?
Yeah, in a sense it does, but in this case I don't see much choice. The
META.yml isn't powerful enough to express all the different prereq sets
a module might have in different situations. For example, a module
might have different prereqs on Win32 than on *nix. Or it might have
different prereqs under perl5.6 than perl5.8. Or in your case, the
prereqs vary based on a selection the user makes at configuration time.
Isn't all of this the reason we had the discussion[1] a little while
back about having complex boolean expressions in requirements?
1. <http://www.nntp.perl.org/group/perl.module-authors/2630/>
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
|
