# from Ron Savage # on Sunday 08 October 2006 03:49 pm: >o I am thinking of some procedure the author, perhaps, could use to > generate the info to add to the meta data, like so: >(1) Probe for compiler >(2) If found, remove compiler's directory from the path, and bugger > the consequences (if only to forestall more red herrings) >(3) Go to (1) to check for more compilers >(4) Now, in a compiler-free environment, try to install the module
How about doing this with an external tool (i.e. a utility or module not in Module::Build) of some sort? If I understand correctly, this is really just a packaging (and possibly third-party-auditing) task. >(5) If it installs, patch meta data to say so >(6) If the install dies, patch meta data to say so What info will it put in the meta data? --Eric -- As an old bass player friend of mine used to say: throw money, don't clap. --Tony Parisi --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------