Eric Wilhelm wrote:
> # from Ron Savage
> # on Saturday 21 March 2009 16:00:
>
>> compiler: mandatory, optional, not_needed?
>>
>> And, yes, I understand that if M::B wants to be all things to all
>> people, we're just talking about the relevance of this new key to Perl
>> modules.
>
> Well, META.yml might like to be all things to all people, but I haven't
> heard from them, so we might as well do perl well.
>
> compiler_required: true|false|maybe
> ?
>
> Is there a situation where a certain sort of compiler is needed? But
> then, maybe that can be handled more easily with an Alien:: package.
Yes, of course. Modules which use C, C++, Fortran, Java, Assembly and Ruby
all exist off the top of my head.
This is just a narrow subset of the problem of how to deal with dependencies
on things which are not Perl modules.
> Hmm, what if there were a module named 'compiler'? Not sure I want to
> play that game through though.
Having module wrappers confirming the existence of external utilities and an
API/config to where they may be found and how they are run may be the simplest
game to play. ExtUtils::CBuilder being one, and possibly the most
complicated, example.
--
s7ank: i want to be one of those guys that types "s/j&jd//.^$ueu*///djsls/sm."
and it's a perl script that turns dog crap into gold.
