On Fri, Jun 12, 2009 at 11:36:31AM -0700, Andy Dougherty wrote: > In the 'ins' branch, build/Makefile.in looks like it's heading down the > same wrong road as parrot. See parrot's TT #700 for more details and a > patch for parrot. I'd suggest a similar approach for rakudo.
Rakudo simply uses parrot_config to get most of its build information, so it seems our options at present are (1) head down the same wrong road as parrot until parrot cleans things up, or (2) implement our our Configure subsystem that is independent of Parrot. #2 doesn't seem all that enticing to me and seems like it will result in a lot of duplication of effort and many places for things to get "out of sync" between the two. So, I'm hoping that someone will soon clean up Parrot's configuration system (especially parrot_config) so that Rakudo can then "head down a similar right road as Parrot". Pm
