Barbie wrote:
From: "Jos I. Boumans" <[EMAIL PROTECTED]>
Why the need for such an immensive framework? to be able to probe for
any type of file/function on any type of OS is not going to be trivial.
To look for every possibility yes that would be emmense. However, I wasn't
expecting to go that far. There are a few cross-platform ways of looking for
libraries and apps, as has been indicated by have_library() and the like. By
refering to Module::Install, I meant the check module would be part of the
distribution, and be called within Makefile.PL/Build.PL before calls to the
appropriate build mechanism.
Although a long way from being done, there is a spec for a small
scripting language[1] that has been discussed and mostly agreed on, at
least experimentally, for describing requirements on modules, external
libs, header files, programs, OS, perl features (threading, large file),
etc. The plan is to include it as part of the META.yml spec and to write
a module[2] that reads, writes, and validates the requirements described
in the META.yml file. With a way to describe all requirements in
META.yml and a module to validate it it would be possible for CPANPLUS
to grab the META.yml, validate it, and then decide whether to download
the actual module. ???
The tentative plan is to put the generic lib, include, program, compiler
detection code in the Probe::* namespace so other modules like
ExtUtils::CBuilder can also access the functionality.
This is all tentative and apparently a good ways off; mostly because I'm
very slow.
Randy.
1. <http://svn.versiondude.net/randys/dEx/trunk/lib/dEx.pm>
2. <http://svn.versiondude.net/randys/CPAN-Metadata/trunk/>
