public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Jones <cbj@gnu.org>
To: Stephen Crawley <crawley@dstc.edu.au>
Cc: John Leuner <jewel@pixie.co.za>, Alex Lau <alex@dentonlive.com>,
	kissme-general@lists.sourceforge.net,
	Mark Wielaard <mark@klomp.org>,
	mauve-discuss@sources.redhat.com
Subject: Re: [Kissme-general] Re: Should I or not submit changes?
Date: Tue, 16 Jul 2002 20:05:00 -0000	[thread overview]
Message-ID: <m3adorunj9.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <200207170047.g6H0l3R11371@piglet.dstc.edu.au>

Stephen Crawley <crawley@dstc.edu.au> writes:

> The problem is that if you run Mauve tests the way that the Mauve README
> file says you should, the key file has to live in the Mauve directory.
> This is real nuisance.  [I can arrange that the Kissme make rules for
> running the Mauve tests copy the key file to the place where Mauve 
> expects it to be ... but that's a HACK.]

I agree.

> HERE are some other beefs that I have with Mauve:
> 
>   *  Mauve's "make clean" doesn't delete the .class files.

Yes.

> 
>   *  Someone has checked some files generated by autoconf, etcetera
>      (configure and Makefile IIRC).   These contain dependencies on
>      the version of autoconf, etcetera used on said person's machine
>      and break on my machine.  These generated files need to be 
>      removed from CVS.

Has always been that way, but I don't know why.  I really dislike
seeing these files checked into CVS.  I even updated them once.

> 
>   *  Mauve needs a global cvsignore file to ignore *.class files and
>      a .cvsignore file on the top directory to ignore the files created
>      by autoconf and configure.

Yes, I'm sure these details need work.  Mauve needs dedicated contributors.

> 
>   *  The Mauve configure.ac metascript should have a --with option for
>      specifying a directory or search path for finding key files.  
>      
>   *  The Mauve makefile should notice when I have edited the current
>      key file, and rebuild the class list file.
> 
>      At the moment, I think that the class list only gets rebuilt 
>      if you change the value of the KEYS environment variable.

Yes, it really sucks to try to use Mauve in certain ways.  If anyone
has loads of time it would probably be more interesting to develop
junit based tests from the classpath source as a start and gradual
port of the Mauve tests to what is usually a more familiar test
framework to developers at large.

Brian
-- 
Brian Jones <cbj@gnu.org>

  reply	other threads:[~2002-07-17  3:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1026843874.3494.68.camel@bapli>
2002-07-16 17:48 ` Stephen Crawley
2002-07-16 20:05   ` Brian Jones [this message]
2002-07-17  2:32     ` Dalibor Topic
2002-07-18  6:21       ` Mark Wielaard
2002-07-18  8:06         ` Dalibor Topic
2002-07-19  3:51         ` Chris Gray
2002-07-18  6:35       ` Brian Jones
2002-07-17  7:13     ` Andrew Haley
2002-07-18  6:32       ` Mark Wielaard
2002-07-18  6:56         ` Andrew Haley
2002-07-18  7:07         ` Dalibor Topic
2002-07-17  8:33   ` Alex Lau
2002-07-17  8:49     ` Stephen Crawley
2002-07-17 12:15       ` Alex Lau
2002-07-17  9:02     ` Dalibor Topic
2002-07-18  6:26     ` John Leuner
2002-07-18  6:00   ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3adorunj9.fsf@lyta.haphazard.org \
    --to=cbj@gnu.org \
    --cc=alex@dentonlive.com \
    --cc=crawley@dstc.edu.au \
    --cc=jewel@pixie.co.za \
    --cc=kissme-general@lists.sourceforge.net \
    --cc=mark@klomp.org \
    --cc=mauve-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).