From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29492 invoked by alias); 12 Apr 2004 04:12:34 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 29474 invoked from network); 12 Apr 2004 04:12:29 -0000 Received: from unknown (HELO ms-smtp-02-eri0.southeast.rr.com) (24.25.9.101) by sources.redhat.com with SMTP; 12 Apr 2004 04:12:29 -0000 Received: from [10.0.0.2] (rdu57-9-048.nc.rr.com [66.57.9.48]) by ms-smtp-02-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id i3C4CFkF009642; Mon, 12 Apr 2004 00:12:15 -0400 (EDT) Subject: Re: Mauve patches. From: "C. Brian Jones" Reply-To: cbj@gnu.org To: Thomas Zander Cc: David Lichteblau , mauve-discuss@sources.redhat.com In-Reply-To: <200404112136.52657.zander@javalobby.org> References: <200404060956.14298.zander@javalobby.org> <200404111919.24816.zander@javalobby.org> <20040411185745.GD21097@lichteblau.com> <200404112136.52657.zander@javalobby.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-p74Be8/MKPvpNg0dX7yP" Message-Id: <1081743135.3175.18.camel@lyta.haphazard.org> Mime-Version: 1.0 Date: Mon, 12 Apr 2004 04:12:00 -0000 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-SW-Source: 2004-q2/txt/msg00022.txt.bz2 --=-p74Be8/MKPvpNg0dX7yP Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Content-length: 2763 On Sun, 2004-04-11 at 15:36, Thomas Zander wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 >=20 > > Unless I misunderstood Thomas' question, he could not compile all of > > Mauve because his script tried to compile _everything_, as opposed to > > those files usually chosen by the standard build system. I would find > > it a little confusing if Mauve provided two build systems, one which > > uses tags and one which does not. >=20 > You did misunderstand my question; > the question is that I created a build system that only tests the classes= I=20 > select (based on ant) and I want it committed; but there seems to be no=20 > maintainer that can comment on, or commit the patch. >=20 > My question therefor (to be exact) was that if some more freedom for=20 > not-yet-initiated coders is allowed, I would like to have a writable=20 > cvs-account which means I can continue working without waiting for more=20 > then a week. Started doing some work over the weekend to add some tests to Mauve based on another software package I've made that has non-Mauve related functionality. Anyway it seems to be somewhat difficult to add something like this to Mauve, that has extensive data sets, a small library not in the gnu.* namespace, etc. I've started by trying to define the problem and generalize on potential solutions. Problems =20 * Cannot be installed (packaged, used repeatedly for various cases from same install) * No integrated pass/fail/expected/unexpected summary * Repeated executions require knowing inner workings of various scripts * Integration of additional libraries difficult at best * Integration of VM specific tests also difficult =20 Solutions =20=20=20=20=20=20=20=20=20 * Change configure script to be installation oriented, similar for Makefile.am (started this already) * New script(s) for running mauve to compile, execute, report results (consider using dejagnu) * Specify java compiler at runtime * Specify vm at runtime * Specify temporary directory at runtime * Specify additional libraries/resources at runtime * Specify additional tests at runtime Basically all the cruft and gorp in configure.in, Makefile.am, choose, etc. gets done over. The TAGS system is broken, it doesn't allow one to specify that a particular test is only valid for 1.1, 1.2, 1.3 and not 1.4+, essential to handle deprecated methods that eventually get removed. I have no problem doing this work, my problem is all the people that depend on the current directory structure, build process, etc. that will scream if something is changed. Anyway I have started the work, when I have a patch I'll let the list review. Don't hold your breath, I'm slow sometimes. :) Thanks, Brian --=20 Brian Jones --=-p74Be8/MKPvpNg0dX7yP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQBAehcecEcmdY33uzYRAh7qAJ0ai1StyZ+EnpP2SGM5oPGSPVEvdQCbBqIq aMfViV5wC9CxVofPo54Uh/c= =c2dE -----END PGP SIGNATURE----- --=-p74Be8/MKPvpNg0dX7yP--