From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15098 invoked by alias); 6 Oct 2003 02:24:27 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 15091 invoked from network); 6 Oct 2003 02:24:26 -0000 Received: from unknown (HELO mail3.panix.com) (166.84.1.74) by sources.redhat.com with SMTP; 6 Oct 2003 02:24:26 -0000 Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail3.panix.com (Postfix) with ESMTP id F3E4F9884F; Sun, 5 Oct 2003 22:24:25 -0400 (EDT) Received: (from kingdon@localhost) by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id h962OP704540; Sun, 5 Oct 2003 22:24:25 -0400 (EDT) Date: Mon, 06 Oct 2003 03:42:00 -0000 Message-Id: <200310060224.h962OP704540@panix5.panix.com> From: Jim Kingdon To: xconq7@sources.redhat.com In-reply-to: (message from Hans Ronne on Sun, 5 Oct 2003 23:27:52 +0200) Subject: Re: Xconq output files References: X-SW-Source: 2003/txt/msg00474.txt.bz2 > And do we really need to put the scores files in a common place > (/var/lib)? Well, getting rid of this would remove the need for xconq to be setgid, which would help with some of the known security holes. I suppose there probably are people who like a common score file (e.g. perhaps that ISP which has cconq installed). But I don't know whether there this is strong enough to warrant keeping the feature. > I think it would make sense to use the xcq extension only for files > (game files) that can be opened by Xconq and the txt extension for all > other text files. I'm not sure which files this would change. Instead of txt, I might just omit an extension (e.g. Xconq.Warnings rather than Xconq.Warnings.txt). But the general idea sounds OK. > * saved games, checkpoints and debug files all go into a "save" directory, > either within the xconq top directory itself (Mac and Windows) or a visible > $HOME/xconq directory on Unix. I guess I'd put these in .xconq. It isn't really normal for an application to hardcode the name of any directory not starting in ".".