On 5/14/07, Ken Williams <[EMAIL PROTECTED]> wrote:
On May 14, 2007, at 2:22 PM, Gabor Szabo wrote: > Hi, > > 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? I agree it would be a good first approximation. A small refinement would be to also add distributions that declare a dependency on ExtUtils::CBuilder or ExtUtils::ParseXS.
That looks to me like a very good technique. It probably can catch almost all cases of distribution with files with .xs, .c or .h extensions and more. For example, I have a distribution named Term-Size-Perl which at build time dynamically generates a C source which is compiled and run. Even though this dependency is needed only at build time, there's no way to escape it, which makes it a hybrid distribution. On the other hand, looking at the distribution files, there's no static C source file. There is a problem with distributions which do not correctly declare its dependencies. Cheers, Adriano
-Ken
