From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 107051 invoked by alias); 13 Jun 2017 19:30:59 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 107017 invoked by uid 89); 13 Jun 2017 19:30:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=our X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 13 Jun 2017 19:30:56 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dKrWi-0002rY-S3 for gdb-patches@sourceware.org; Tue, 13 Jun 2017 15:30:59 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:48669) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dKrWi-0002rB-OM; Tue, 13 Jun 2017 15:30:56 -0400 Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4874 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dKrWf-00008X-Pw; Tue, 13 Jun 2017 15:30:56 -0400 Date: Tue, 13 Jun 2017 19:30:00 -0000 Message-Id: <837f0f4ri0.fsf@gnu.org> From: Eli Zaretskii To: Simon Marchi CC: tom@tromey.com, orgads@gmail.com, gdb-patches@sourceware.org In-reply-to: <27c866069cdcc4dc4b5e3cf5d3affe83@polymtl.ca> (message from Simon Marchi on Tue, 13 Jun 2017 19:29:21 +0200) Subject: Re: [PATCH] Fix python compatibility with old versions of GDB Reply-to: Eli Zaretskii References: <227db26304444bfb5ed8f699ab67e7fd@polymtl.ca> <87o9tsozn6.fsf@pokyo> <83ink03q1w.fsf@gnu.org> <27c866069cdcc4dc4b5e3cf5d3affe83@polymtl.ca> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-IsSubscribed: yes X-SW-Source: 2017-06/txt/msg00402.txt.bz2 > Date: Tue, 13 Jun 2017 19:29:21 +0200 > From: Simon Marchi > Cc: Tom Tromey , orgads@gmail.com, > gdb-patches@sourceware.org > > On 2017-06-13 16:44, Eli Zaretskii wrote: > > FWIW, I always configure GDB to use a version-specific data-directory, > > because I leave old GDB versions (renamed) on my system, so I could > > still use them after installing a new version. E.g., if the new > > version turns out to have a bug. I would actually be happier if we > > changed our installation scripts to do that by default, because the > > scripts are almost never backward-compatible IME. > > Can you give more details on what you think could/should be done by > default? I'd like the data-directory be version-dependent, i.e. be /usr/share/gdb/VERSION/ and not just /usr/share/gdb/. But I wonder why that isn't the default behavior, as the files we install into data-directory are version-dependent and incompatible with other GDB versions. > For such a use case, I would compile each gdb with a separate prefix > (e.g. --prefix=/opt/gdb/), which would give each install its > own data directory. That's close to what I do, as described above. I just don't set "--prefix", because that would affect directories like bindir, mandir, infodir, which I don't want to keep separately for each version.