James Keenan via RT schrieb:
I'm trying to see if we can move this ticket toward resolution. I think
that it has remained unresolved for so long because the original post
originally called for two steps: (a) removal from Configure.pl of
configuration steps which probed for features only used in specific
language implementations; (b) development of a way to conduct such
language-specific probes in the language directory trees after 'perl
Configure.pl' and 'make' have been run.
There were two specific steps cited for removal per (a): auto::python
and auto::m4. By June of this year I had removed both of those from
Parrot configuration.
So that leaves us with (b). particle wrote: "languages/dotnet/ has its
own configure.pl, and m4, plumhead, etc. should follow that model."
Barney responded: "One thing that held me back from using something
like 'dotnet/Configure.pl' was that 'dotnet/Configure.pl' currently
needs to be explicitly called after the main 'Configure.pl' has run.
This is bad for universal languages testing."
And that's where discussion left off three months ago. I am
recommending the following:
(1) Mark this ticket resolved.
(2) Conduct discussion on list or IRC as to the best architecture/model
for language-specific probes.
(3) Once we've come to such resolution on (2), open a new RT to
implement what we've decided.
particle, Barney: Any objections?
Sounds good.
An example for a language specific config probe could be put
mk_language_shell.pl.
Regards,
Bernhard
Thank you very much.
kid51
