From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9892 invoked by alias); 17 Jul 2002 00:48:13 -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 9878 invoked from network); 17 Jul 2002 00:48:12 -0000 Received: from unknown (HELO piglet.dstc.edu.au) (130.102.176.1) by sources.redhat.com with SMTP; 17 Jul 2002 00:48:12 -0000 Received: from dstc.edu.au (soluble.dstc.edu.au [130.102.176.43]) by piglet.dstc.edu.au (8.11.3/8.11.3) with ESMTP id g6H0l3R11371; Wed, 17 Jul 2002 10:47:03 +1000 (EST) Message-Id: <200207170047.g6H0l3R11371@piglet.dstc.edu.au> To: John Leuner cc: Alex Lau , kissme-general@lists.sourceforge.net, crawley@dstc.edu.au, Mark Wielaard , mauve-discuss@sources.redhat.com Subject: Re: [Kissme-general] Re: Should I or not submit changes? In-Reply-To: Message from John Leuner of "16 Jul 2002 19:24:33 +0100." <1026843874.3494.68.camel@bapli> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Jul 2002 17:48:00 -0000 From: Stephen Crawley X-Scanned-By: MIMEDefang 1.0 (http://www.roaringpenguin.com/mimedefang/) X-SW-Source: 2002-q3/txt/msg00001.txt.bz2 > I added your changes, but I can't figure out how to get the .in files to > be turned into .sh files. They would simply need to be added to the AC_CONFIG_FILES macro call in Kissme's configure.ac file. However ... I've looked at Alex's scripts, and concluded that it would be better to use the 'mauve-kissme' key file that Mark Wielaard emailed last week, especially if we can put that file into CVS. 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.] Here are some other beefs that I have with Mauve: * Mauve's "make clean" doesn't delete the .class files. * 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. * 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. * 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. -- Steve