On Thu, Apr 19, 2007 at 02:28:27PM +0100, Martin Guy wrote: > >1) you revert your last changes in as_value/ASHandlers.cpp > What's the problem? > > >2) we work toward making "make check" work for you > > > >A quick way for (2) is install Ming from current CVS. > makeswf --version > $Id: makeswf.c,v 1.31 2006/12/12 23:36:10 strk Exp $ > > Is that really too old? It seems unwise to rely on unstable software > under development as the testsuite for a new product.
We accept any 0.4.x Ming version. Some tests are just skipped if not supported by the version you have. 0.3 is not supported for a single reason: lack of 'ming-config', if it wasn't for this we'd support 0.3 too. What you have is a CVS snapshot, we can't support CVS snapshots too.. > I confess I don't really understand what your problem is, what with > all these public accusations of incompetence and ranting. Mind you, > the atmosphere in the group since I have known it has been sneering > and competitive instead of cooperative, so I am discounting the > offensiveness as part of that sad game. Sorry about that, I'm just pissed off that while hacking and continuosly checking by running 'make check' I find myself unable to verify my own hacks by running 'make check' again since somebody else broke it. > I mean, every time I make a commit you start ranting at me. What *is* > your problem? I only rant if you commit changes that break the existing testsuite. Being able to run the testsuite should be top priority for any committer. I can understand temporary problems with it, but I can't stand breaking things twice in a few hours. It makes the work of other developers harder. --strk; _______________________________________________ Gnash-commit mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-commit
