On Sat, 17 Nov 2007, James E Keenan wrote:
>
> On Nov 17, 2007, at 11:25 AM, Andy Dougherty via RT wrote:
>
> >
> > I used something like
> > perl5.8 Configure.pl --cc=gcc --link=gcc --ld=gcc --ask
> >
> > (the --ask is because I also changed the ccflags, ldflags, and libs to
> > match gcc, and the --ask version prompts with a default that is almost,
> > but not quite, what I want.)
>
> How wedded are you to the continued existence of the --ask option, i.e., to
> the interactive mode in Parrot configuration?
As long as it is replaced by something that's roughly equally easy to use,
I don't really care. The biggest problem with automated configuration
scripts is that when they guess wrong, they can often be a real pain to
correct. I've had to manually edit far more "automatic" scripts than I
care to remember. Interactive steps offer an easy-to-use way to fix up
such wrong guesses. But command-line (or start-up file) options could
also fit the same bill, I suppose, if they are sufficiently flexible and
well-documented.
> I suspect that anyone who has to
> reconfigure Parrot repeatedly can be persuaded to put all the options up
> front. If that's the case, then we could scrap the interactive mode -- and I
> could write much more robust tests!
Do remember, however, that the ultimate audience is those who will only
have to configure Parrot once.
--
Andy Dougherty [EMAIL PROTECTED]
