Re: recent dejagnu changes

[Jim Ingham <jingham at apple dot com>]

Also sprach Jimmy Guo:

> If I may, let's retire this thread ... there're assumptions and
> perceptions I made, both in the dejagnu design and in the working
> process, that caused the dejagnu regression and the following
> communications that's less than desirable ... and my apologies to the
> GCC project which wasted time tracking my changes down :)
> 
> Changes to odd components like dejagnu with little documentation nor
> visibility (until it breaks) are dangerous.  Fortunately I don't have
> further changes in this area ... as to the couple of patches, I'm sure
> we can work it through without further disturbance.  It's never too much
> to be reminded that working on a OpenSource project requires extra
> prudence and patience ... which is something the HP WDB team is prepared
> to accept.
> 
> - Jimmy Guo, guo@cup.hp.com
> 
> 

Before this thread is entirely retired, it is a little worthwhile to point
out that it is REALLY unfortunate that the testing framework for a set of
tools as important as gdb & gcc has NO maintainer (and is in such generally
poor shape as Dejagnu undoubtly is).  Now, I am not myself volunteering - I
have a spare time Free Software project already and no spare time to boot.
And I realize that some similar thing is probably true of everyone on this
list.  However, I also bet that many of the people on this list have started
out to make some simple change to dejagnu, and ended up wasting hours
tearing their hair out over this or that infelicity in the Dejagnu source...

This is a very unsatisfactory situation, and we need to do something about
it.  I have no solution, just thought it is worthwhile to point out that the
problem is more serious than just a mild collision between a couple of users
of Dejagnu..

Jim
-- 
Jim Ingham                                 jingham@apple.com
Apple Computer