On Sun, 2 Sep 2007, Paul Cochrane wrote:
> On 02/09/07, James E Keenan <[EMAIL PROTECTED]> wrote:
> > Could we get some discussion of the pros and cons of different
> > alternatives?
> >
> > -- Should Configure.pl die when one of its steps fail?
> > -- Should it not die, but exit with a nonzero exit code?
> > -- Should it not die, but trigger a different message on STDOUT?
> > -- Or is the current setup, on balance, best suited for our needs?
>
> There are definitely cases in which we should barf, although I'm not
> sure if we should *always* barf. For instance, if Configure.pl can't
> find a C-compiler there isn't much use in continuing, however, to
> continue is the current behaviour.
It all depends on how important the failure is.
It should be possible for Configure.pl to die if the failure is
sufficiently important. For example, it should die if there is no C
compiler found. It should not die if bison isn't found.
> I have the vague feeling that this
> question has been raised before, but no firm answer has arisen...
Oh it's been discussed aplenty, with patches and suggestions and
everything. All that remains is to put the pieces together, but no one
(myself included) has had both the time and inclination to do just that.
See RT #41168.
--
Andy Dougherty [EMAIL PROTECTED]
