From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 85992 invoked by alias); 13 Jun 2017 14:44:58 -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 85976 invoked by uid 89); 13 Jun 2017 14:44:57 -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=ime, happier, our, policy 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 14:44:55 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dKn3u-0004Tt-4z for gdb-patches@sourceware.org; Tue, 13 Jun 2017 10:44:58 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44544) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dKn3u-0004Tp-1Z; Tue, 13 Jun 2017 10:44:54 -0400 Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4478 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dKn3t-0003m4-BH; Tue, 13 Jun 2017 10:44:53 -0400 Date: Tue, 13 Jun 2017 14:44:00 -0000 Message-Id: <83ink03q1w.fsf@gnu.org> From: Eli Zaretskii To: Tom Tromey CC: simon.marchi@polymtl.ca, orgads@gmail.com, gdb-patches@sourceware.org In-reply-to: <87o9tsozn6.fsf@pokyo> (message from Tom Tromey on Tue, 13 Jun 2017 06:11:57 -0600) Subject: Re: [PATCH] Fix python compatibility with old versions of GDB Reply-to: Eli Zaretskii References: <227db26304444bfb5ed8f699ab67e7fd@polymtl.ca> <87o9tsozn6.fsf@pokyo> 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/msg00386.txt.bz2 > From: Tom Tromey > Cc: Orgad Shaneh , gdb-patches@sourceware.org > Date: Tue, 13 Jun 2017 06:11:57 -0600 > > >>>>> "Simon" == Simon Marchi writes: > > >> Practically the data-directory is mostly backwards-compatible, except > >> this small part which I found (there might be others which I didn't > >> find). With this patch, I'm able to run GDB 7.8 with the latest > >> data-directory. > > >> Is there a reason not to accept it? > > Simon> I'd like to know what other maintainers think about this. We may have > Simon> already faced this situation before and taken a decision which I'm not > Simon> aware of. Otherwise, we need to take it now. > > I think it doesn't make sense to have a policy allowing the sharing of > installed Python scripts across versions. If this were a policy then it > would mean that the scripts could never use new features of gdb's Python > layer -- but that's clearly an absurd result. 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.