From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26736 invoked by alias); 22 Aug 2006 18:03:27 -0000 Received: (qmail 26715 invoked by uid 48); 22 Aug 2006 18:03:26 -0000 Date: Tue, 22 Aug 2006 18:03:00 -0000 Message-ID: <20060822180326.26713.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libgcj/27890] [4.2 regression] lib/logging.properties pollutes common namespace In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "david at jpackage dot org" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2006-q3/txt/msg00226.txt.bz2 List-Id: ------- Comment #11 from david at jpackage dot org 2006-08-22 18:03 ------- I am just voicing my support for comment #2. In practice, we see a problem when installing both classpath and gcj on the same system, since they both install classpath.security and logging.properties files. Ideally, both classpath and gcj could share these files, or perhaps not and each JVM should be able to have its own configuration. Even if that's the case, these files look like global configuration files, that apply to any JVM using classpath or classpath derivatives. The location should likely be changed in either case. These are configuration files and likely need to be writable, so they should not be placed under /usr. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27890