Gabor Szabo wrote:
I would like to create a list of modules that need compilations
as opposed to those that are pure perl
Is checking for a file with .xs .c or .h extension in the distribution
the correct thing to do? Is there a better way to collect this information or is it
already available somewhere?
Some modules can work without XS part. Well-known example is
Scalar-List-Utils that detects if compiler is available and can work
both ways. But this is bad example because it's functionality is changed
depending on it. Net-DNS, Template-Toolkit use XS for speed.
You can try installing them without a compiler.
There is PAUSE "DLSIP Definition", but it is only for registered modules
and may be inaccurate.
In addition I would located modules that have dependecies that are not
available on CPAN. (e.g. most of the DBD::* modules are such
but DBD::SQLite is not such a module as it includes all the C code of
SQLite)
You can analyse rpm/deb/etc packages in different OS for dependencies :).
--
WBR,
Alexandr mailto:[EMAIL PROTECTED]
